Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b2786312efee34dc4dcb903f38f6b332e9e4408a31f682d3af7f81c30775c70

Tx prefix hash: 4d864b56d87fa1035ceb19ee43d5c180fb033466d68d3aefccce1785349d7121
Tx public key: 1395ca0cefe93f0e6123b17c718c73d566c0b8c747ac8b2abfd3973bf308bd8e
Timestamp: 1707336588 Timestamp [UCT]: 2024-02-07 20:09:48 Age [y:d:h:m:s]: 01:049:03:13:29
Block: 952569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296152 RingCT/type: yes/0
Extra: 011395ca0cefe93f0e6123b17c718c73d566c0b8c747ac8b2abfd3973bf308bd8e0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80402b67a5a409086835164662b9d921f38c3b9aef3121582e26bc5161d5111a 0.600000000000 1411621 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": 952579, "vin": [ { "gen": { "height": 952569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80402b67a5a409086835164662b9d921f38c3b9aef3121582e26bc5161d5111a" } } ], "extra": [ 1, 19, 149, 202, 12, 239, 233, 63, 14, 97, 35, 177, 124, 113, 140, 115, 213, 102, 192, 184, 199, 71, 172, 139, 42, 191, 211, 151, 59, 243, 8, 189, 142, 2, 17, 0, 0, 0, 5, 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