Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bab8de40602c11c9f765a878b8bc06c507d9a9d5b6b0bf977c185388afd3bf2e

Tx prefix hash: 3217d13feb806e054dce83bef5acc4439369dd83b633ea12eb6db5fb04d3ce47
Tx public key: 824037e20604a1a8dfe1ecdbc929e275372744727bb0ebd67a245fdf76f93692
Timestamp: 1729684402 Timestamp [UCT]: 2024-10-23 11:53:22 Age [y:d:h:m:s]: 01:028:02:36:47
Block: 1137817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278471 RingCT/type: yes/0
Extra: 01824037e20604a1a8dfe1ecdbc929e275372744727bb0ebd67a245fdf76f93692021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f977c4b82c949ee07d231ad96b303d42156f4d8595c0905d4da5b8d6caeba763 0.600000000000 1621380 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": 1137827, "vin": [ { "gen": { "height": 1137817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f977c4b82c949ee07d231ad96b303d42156f4d8595c0905d4da5b8d6caeba763" } } ], "extra": [ 1, 130, 64, 55, 226, 6, 4, 161, 168, 223, 225, 236, 219, 201, 41, 226, 117, 55, 39, 68, 114, 123, 176, 235, 214, 122, 36, 95, 223, 118, 249, 54, 146, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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