Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f32b1358d7128450b55e1d06de6decef82d8edd51d9cbc85d71e496c03d37089

Tx prefix hash: 24da040bdf07caa127c7e51ab3808d128357c05a4b42a005a0144ea3a216e529
Tx public key: 0ae605ff7abf2c2dc610c20ef26c03ac86dd43c0ee7ad3477cfbfa66b83f1e55
Timestamp: 1704312887 Timestamp [UCT]: 2024-01-03 20:14:47 Age [y:d:h:m:s]: 01:161:09:12:48
Block: 927515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376425 RingCT/type: yes/0
Extra: 010ae605ff7abf2c2dc610c20ef26c03ac86dd43c0ee7ad3477cfbfa66b83f1e550211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbfd3157ef8b3f00840da5da22dbe5910feb8bc96d8a74fd6051392804df472c 0.600000000000 1385351 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": 927525, "vin": [ { "gen": { "height": 927515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbfd3157ef8b3f00840da5da22dbe5910feb8bc96d8a74fd6051392804df472c" } } ], "extra": [ 1, 10, 230, 5, 255, 122, 191, 44, 45, 198, 16, 194, 14, 242, 108, 3, 172, 134, 221, 67, 192, 238, 122, 211, 71, 124, 251, 250, 102, 184, 63, 30, 85, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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