Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f69d256ca7f8fd2b5cc67af3519a292c9c9e82f12920526d97c332aace16c75b

Tx prefix hash: 0dc2497a7468a47c99286d063de096ff318f4284f8ca6418e249e72ad841fb79
Tx public key: 9ecec511d672f35b4f8dbe12fac93dc6fddfe6b630d03b070c73bc7b500e926b
Timestamp: 1719509466 Timestamp [UCT]: 2024-06-27 17:31:06 Age [y:d:h:m:s]: 00:180:21:41:22
Block: 1053479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129472 RingCT/type: yes/0
Extra: 019ecec511d672f35b4f8dbe12fac93dc6fddfe6b630d03b070c73bc7b500e926b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8faa3dddda4104f6516877698b427b3581217317fa6bc1a020d05a1a8da1903 0.600000000000 1523826 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": 1053489, "vin": [ { "gen": { "height": 1053479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8faa3dddda4104f6516877698b427b3581217317fa6bc1a020d05a1a8da1903" } } ], "extra": [ 1, 158, 206, 197, 17, 214, 114, 243, 91, 79, 141, 190, 18, 250, 201, 61, 198, 253, 223, 230, 182, 48, 208, 59, 7, 12, 115, 188, 123, 80, 14, 146, 107, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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