Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0419619052ed14d867ed09977a5f5e34fe080772886ca43214eb7fe35947b1f7

Tx prefix hash: 02f6883d9d4b8b3ce451917c6d1d6d0421f7c9f1345317258c44f525cd5bec3c
Tx public key: c378f6e170cfea71a89dc87acadec5eaae3419f904fd71bf694f9d4a9c437d1a
Timestamp: 1736790474 Timestamp [UCT]: 2025-01-13 17:47:54 Age [y:d:h:m:s]: 00:155:23:24:50
Block: 1196619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111174 RingCT/type: yes/0
Extra: 01c378f6e170cfea71a89dc87acadec5eaae3419f904fd71bf694f9d4a9c437d1a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 191a6db2ee748e3728d1bcb4f42bbdde8fdd4fdb18b6b3517550d351da2ba158 0.600000000000 1683220 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": 1196629, "vin": [ { "gen": { "height": 1196619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "191a6db2ee748e3728d1bcb4f42bbdde8fdd4fdb18b6b3517550d351da2ba158" } } ], "extra": [ 1, 195, 120, 246, 225, 112, 207, 234, 113, 168, 157, 200, 122, 202, 222, 197, 234, 174, 52, 25, 249, 4, 253, 113, 191, 105, 79, 157, 74, 156, 67, 125, 26, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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