Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd39eb7c38fc295017691f44c87f7629256ebe4882b3620a2944a72c7afc4035

Tx prefix hash: 6793722be4a7a64ae355d6985efc07fdc9d5a16b1c8b3bd8fb270aa66a3350ff
Tx public key: 63e6ef598befb731e3ef8e902ab1f27ba7c476a746cd01708a048fb118f4ab08
Timestamp: 1696575547 Timestamp [UCT]: 2023-10-06 06:59:07 Age [y:d:h:m:s]: 02:036:20:19:15
Block: 863551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545973 RingCT/type: yes/0
Extra: 0163e6ef598befb731e3ef8e902ab1f27ba7c476a746cd01708a048fb118f4ab080211000000034b8f5122000000000000000000

1 output(s) for total of 0.844689502000 dcy

stealth address amount amount idx
00: a3224e0f165486c2342f613b7b321500902a02760bd085fbf45e588e659fe7b6 0.844689502000 1318011 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": 863561, "vin": [ { "gen": { "height": 863551 } } ], "vout": [ { "amount": 844689502, "target": { "key": "a3224e0f165486c2342f613b7b321500902a02760bd085fbf45e588e659fe7b6" } } ], "extra": [ 1, 99, 230, 239, 89, 139, 239, 183, 49, 227, 239, 142, 144, 42, 177, 242, 123, 167, 196, 118, 167, 70, 205, 1, 112, 138, 4, 143, 177, 24, 244, 171, 8, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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