Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbb4d38ef268785c052d8da2dc7529b4378e0e705f5f3e611ee13a16bb96ee57

Tx prefix hash: b7ad38f387501df16444075591cf4a6e1bd74ead6d072d497d3a9fd5254a43d2
Tx public key: 92ff042ce69c244d17791444b23b82942ac9c9c199603326f5e3519471da7563
Timestamp: 1699459006 Timestamp [UCT]: 2023-11-08 15:56:46 Age [y:d:h:m:s]: 01:361:18:31:59
Block: 887270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517453 RingCT/type: yes/0
Extra: 0192ff042ce69c244d17791444b23b82942ac9c9c199603326f5e3519471da7563021100000011faf35c9c000000000000000000

1 output(s) for total of 0.704865361000 dcy

stealth address amount amount idx
00: 979ad356c3702bd9e5f429a19ba6c6c97d05cddf8038b77ef95ae01fda4a1006 0.704865361000 1343139 of 0

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": 887280, "vin": [ { "gen": { "height": 887270 } } ], "vout": [ { "amount": 704865361, "target": { "key": "979ad356c3702bd9e5f429a19ba6c6c97d05cddf8038b77ef95ae01fda4a1006" } } ], "extra": [ 1, 146, 255, 4, 44, 230, 156, 36, 77, 23, 121, 20, 68, 178, 59, 130, 148, 42, 201, 201, 193, 153, 96, 51, 38, 245, 227, 81, 148, 113, 218, 117, 99, 2, 17, 0, 0, 0, 17, 250, 243, 92, 156, 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