Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08418259c4143412513138742408eafb950ee2c50bfc9a6095b9820062b95df3

Tx prefix hash: d909e7e40e6e6caea5fb99e2c028c9cb4d137528028e0c98e5319e6eb7552efb
Tx public key: a42926fbe2cdfdd6912b7e3d078d3c17ec592d7af2826ecb90080c437e448098
Timestamp: 1702521710 Timestamp [UCT]: 2023-12-14 02:41:50 Age [y:d:h:m:s]: 01:073:01:54:16
Block: 912648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313331 RingCT/type: yes/0
Extra: 01a42926fbe2cdfdd6912b7e3d078d3c17ec592d7af2826ecb90080c437e44809802110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e53157d9b9b0fabe10e7e20c8bad712430f4a9380920288f88e01545527eb18b 0.600000000000 1369880 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": 912658, "vin": [ { "gen": { "height": 912648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e53157d9b9b0fabe10e7e20c8bad712430f4a9380920288f88e01545527eb18b" } } ], "extra": [ 1, 164, 41, 38, 251, 226, 205, 253, 214, 145, 43, 126, 61, 7, 141, 60, 23, 236, 89, 45, 122, 242, 130, 110, 203, 144, 8, 12, 67, 126, 68, 128, 152, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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