Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ce422e01aafeb5e112503587c0e5ef768ee58745cd0e800c964d2df890fd7654

Tx prefix hash: 6c205dd560e5612f0c280570140b316c48591cc9083d9e26ef39598d2b334884
Tx public key: fec089ea73abf5c6acbf1aea0c575ca71af0c5e7ea2ba47892a09559e2956e41
Timestamp: 1787356872 Timestamp [UTC]: 2026-08-22 00:01:12 Age [y:d:h:m:s]: 00:087:03:53:17
Block: 1618545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 61577 RingCT/type: yes/0
Extra: 01fec089ea73abf5c6acbf1aea0c575ca71af0c5e7ea2ba47892a09559e2956e410208cbfbfda509f002d2

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a2aff4f09eaf5f4a0ead9712998160b62740d8b907d3f78e23741edefb3d06bc 0.000600000000 2108565 of 15 <c9>

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1618555, "vin": [ { "gen": { "height": 1618545 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "a2aff4f09eaf5f4a0ead9712998160b62740d8b907d3f78e23741edefb3d06bc", "view_tag": "c9" } } } ], "extra": [ 1, 254, 192, 137, 234, 115, 171, 245, 198, 172, 191, 26, 234, 12, 87, 92, 167, 26, 240, 197, 231, 234, 43, 164, 120, 146, 160, 149, 89, 226, 149, 110, 65, 2, 8, 203, 251, 253, 165, 9, 240, 2, 210 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: