Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89a2ff53a002d3275c55cb87ad633dff6f9b2904e8abfc3050879f48e39f23de

Tx prefix hash: abb9b74444e6bc08bc7fab74873d1564fc86e1afad8edade80e8789b34eb2b21
Tx public key: d047a24e0f50a51f28a5b7ec251bc1e997241a8e92885479ba6e5634fba960d8
Timestamp: 1758390740 Timestamp [UTC]: 2025-09-20 17:52:20 Age [y:d:h:m:s]: 00:233:06:58:47
Block: 1372718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159003 RingCT/type: yes/0
Extra: 01d047a24e0f50a51f28a5b7ec251bc1e997241a8e92885479ba6e5634fba960d8021100000001ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 71c6da624b31d6e651523c7e135530af24131221bf19f476d20252d85ad36c12 0.000600000000 1860803 of 15 -

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": 1372728, "vin": [ { "gen": { "height": 1372718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71c6da624b31d6e651523c7e135530af24131221bf19f476d20252d85ad36c12" } } ], "extra": [ 1, 208, 71, 162, 78, 15, 80, 165, 31, 40, 165, 183, 236, 37, 27, 193, 233, 151, 36, 26, 142, 146, 136, 84, 121, 186, 110, 86, 52, 251, 169, 96, 216, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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