Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cffc4673be6d1dd841df1da37672c69f6ba2c40c4329632d3b1d2c20c424f36

Tx prefix hash: dd049827a8e967b00fff1383b32a91a51c5bd2caeefdef1993db068dba2cd7ea
Tx public key: 5d629e3d5968e6172ce5bf51e503d65dc792a4279a5ff58251ffaf38135f1415
Timestamp: 1737419846 Timestamp [UCT]: 2025-01-21 00:37:26 Age [y:d:h:m:s]: 00:336:19:26:21
Block: 1201786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238296 RingCT/type: yes/0
Extra: 015d629e3d5968e6172ce5bf51e503d65dc792a4279a5ff58251ffaf38135f14150211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad328df38e144ae9327d3af726afeeb2d6794e9e4e4c01351a589290bf33a4a1 0.600000000000 1688443 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": 1201796, "vin": [ { "gen": { "height": 1201786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad328df38e144ae9327d3af726afeeb2d6794e9e4e4c01351a589290bf33a4a1" } } ], "extra": [ 1, 93, 98, 158, 61, 89, 104, 230, 23, 44, 229, 191, 81, 229, 3, 214, 93, 199, 146, 164, 39, 154, 95, 245, 130, 81, 255, 175, 56, 19, 95, 20, 21, 2, 17, 0, 0, 0, 3, 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