Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39ab4e538b2d16d36bcf826247afa296b3ce89f80080d21caad529f6ac6d06df

Tx prefix hash: f879f6b762d14ba45320a08adf1a4361fe907d8c5e559b8a267189dce8c5e056
Tx public key: 6b884314bfb9b8c4cac117c2c0e0dc6841d71661c156ed29b3c0b57118b08bff
Timestamp: 1709851732 Timestamp [UCT]: 2024-03-07 22:48:52 Age [y:d:h:m:s]: 00:231:13:31:31
Block: 973432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165820 RingCT/type: yes/0
Extra: 016b884314bfb9b8c4cac117c2c0e0dc6841d71661c156ed29b3c0b57118b08bff0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad9af650675f838d2a524c203512b48bc28203f81d3554c27cda9e051516e6b9 0.600000000000 1433367 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": 973442, "vin": [ { "gen": { "height": 973432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad9af650675f838d2a524c203512b48bc28203f81d3554c27cda9e051516e6b9" } } ], "extra": [ 1, 107, 136, 67, 20, 191, 185, 184, 196, 202, 193, 23, 194, 192, 224, 220, 104, 65, 215, 22, 97, 193, 86, 237, 41, 179, 192, 181, 113, 24, 176, 139, 255, 2, 17, 0, 0, 0, 1, 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