Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56dc9608bd4f8a8e5892749fa74c564555b01c8fff16675aa00fc05fa8c5f6ed

Tx prefix hash: 8864bc028961c141ca6f68e28fd58d6f74f8815853c27163e40c79d5b65d1686
Tx public key: 4e18905fc7f5d6add971f347ace9e74b57622692943908d901bd06eb7eaacd36
Timestamp: 1782879670 Timestamp [UTC]: 2026-07-01 04:21:10 Age [y:d:h:m:s]: 00:144:11:42:40
Block: 1572005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 111489 RingCT/type: yes/0
Extra: 014e18905fc7f5d6add971f347ace9e74b57622692943908d901bd06eb7eaacd360208d22dcd180c99f3c4

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5eb004f7aabcd1bc70d05039e174c534f3d04f3b0ad7aaec03be6961c66a1bda 0.000600000000 2061985 of 15 <f2>

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": 1572015, "vin": [ { "gen": { "height": 1572005 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "5eb004f7aabcd1bc70d05039e174c534f3d04f3b0ad7aaec03be6961c66a1bda", "view_tag": "f2" } } } ], "extra": [ 1, 78, 24, 144, 95, 199, 245, 214, 173, 217, 113, 243, 71, 172, 233, 231, 75, 87, 98, 38, 146, 148, 57, 8, 217, 1, 189, 6, 235, 126, 170, 205, 54, 2, 8, 210, 45, 205, 24, 12, 153, 243, 196 ], "rct_signatures": { "type": 0 } }


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