Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4218c96e5c51b40ad117b6664f3370177a0f993b347b1e7d19fe9ff72967845

Tx prefix hash: 9e4cd044b8e4cad6a7489d2e437a07823ee8eb213a1a940705d3858e2863b623
Tx public key: 40f33ba0753a6d4c96a7fad099e090bd0fcb5f7118c9b25546370de2c445b6d2
Timestamp: 1760072145 Timestamp [UCT]: 2025-10-10 04:55:45 Age [y:d:h:m:s]: 00:031:14:51:20
Block: 1386650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22648 RingCT/type: yes/0
Extra: 0140f33ba0753a6d4c96a7fad099e090bd0fcb5f7118c9b25546370de2c445b6d2021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b71664f006138a8434f4c9fa35449224b2cf8220a451b58487bdbc94ef15a8b5 0.600000000000 1874821 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 dinasty-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": 1386660, "vin": [ { "gen": { "height": 1386650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b71664f006138a8434f4c9fa35449224b2cf8220a451b58487bdbc94ef15a8b5" } } ], "extra": [ 1, 64, 243, 59, 160, 117, 58, 109, 76, 150, 167, 250, 208, 153, 224, 144, 189, 15, 203, 95, 113, 24, 201, 178, 85, 70, 55, 13, 226, 196, 69, 182, 210, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8