Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd5c2b3d0e7ab7f243e742e289fbce99b71c10a7100a3bfb75ea0576a676318a

Tx prefix hash: 875f28edbeb911296b1ab85de1f1b4132e94761f9cea853b1e684f0f2308d7c3
Tx public key: 63fa9f4117995f28ad899aef1c83fc2a3f9e0751d34720cc6ea91737625cd671
Timestamp: 1736336121 Timestamp [UCT]: 2025-01-08 11:35:21 Age [y:d:h:m:s]: 00:348:12:42:57
Block: 1192850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246649 RingCT/type: yes/0
Extra: 0163fa9f4117995f28ad899aef1c83fc2a3f9e0751d34720cc6ea91737625cd67102110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2abfe1461c0c5cadda3db62a5d7bf5f5aedd17d3dc78196f34a21645f143c050 0.600000000000 1679407 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": 1192860, "vin": [ { "gen": { "height": 1192850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2abfe1461c0c5cadda3db62a5d7bf5f5aedd17d3dc78196f34a21645f143c050" } } ], "extra": [ 1, 99, 250, 159, 65, 23, 153, 95, 40, 173, 137, 154, 239, 28, 131, 252, 42, 63, 158, 7, 81, 211, 71, 32, 204, 110, 169, 23, 55, 98, 92, 214, 113, 2, 17, 0, 0, 0, 10, 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