Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 536e4236f459b2b9b1245e935d518eae7bde6221ba6e2bcfb4d405bbdddfe5ab

Tx prefix hash: 0846cff10a3d7331c969ab73d26e44d675d1c316d92d9371fd51350c53596e20
Tx public key: e1b4af7fbf6d244445f351923c96bf7486532a343eeb0bc44a54bb69acc2fd5e
Timestamp: 1715774303 Timestamp [UCT]: 2024-05-15 11:58:23 Age [y:d:h:m:s]: 00:348:11:33:18
Block: 1022527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249103 RingCT/type: yes/0
Extra: 01e1b4af7fbf6d244445f351923c96bf7486532a343eeb0bc44a54bb69acc2fd5e0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d70050b6981aed62de1f456e7554a353fafaf01494631d1ff3f3606421d17fbe 0.600000000000 1487158 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": 1022537, "vin": [ { "gen": { "height": 1022527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d70050b6981aed62de1f456e7554a353fafaf01494631d1ff3f3606421d17fbe" } } ], "extra": [ 1, 225, 180, 175, 127, 191, 109, 36, 68, 69, 243, 81, 146, 60, 150, 191, 116, 134, 83, 42, 52, 62, 235, 11, 196, 74, 84, 187, 105, 172, 194, 253, 94, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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