Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df64a0358df1fde65b6081fe1f1bb87b9710b2d07d6cbab4378ab5bde5afae48

Tx prefix hash: a9ea9910e1d5185b107ba034c3a1d4f838d3413f57f252719c54278ad4ad8319
Tx public key: 26a4afa9c7f8972ba38ccf33947e0e69b42522de222703de692969e47eb299c6
Timestamp: 1720212446 Timestamp [UCT]: 2024-07-05 20:47:26 Age [y:d:h:m:s]: 00:200:22:32:47
Block: 1059312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143739 RingCT/type: yes/0
Extra: 0126a4afa9c7f8972ba38ccf33947e0e69b42522de222703de692969e47eb299c60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c8461646e3df6d68ae5d240fc3711e4a693fd6f81f2813bc584fdeabdf40623 0.600000000000 1529779 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": 1059322, "vin": [ { "gen": { "height": 1059312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c8461646e3df6d68ae5d240fc3711e4a693fd6f81f2813bc584fdeabdf40623" } } ], "extra": [ 1, 38, 164, 175, 169, 199, 248, 151, 43, 163, 140, 207, 51, 148, 126, 14, 105, 180, 37, 34, 222, 34, 39, 3, 222, 105, 41, 105, 228, 126, 178, 153, 198, 2, 17, 0, 0, 0, 1, 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