Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 933dcd00758de386e69b6b8e5d5dc326d6919d0daee281457d01b416c917f672

Tx prefix hash: 8bf52c702f41fd73977a1ae7cff2dc7a24b9910d80c19084825160a6b7dd99c8
Tx public key: a89a64118788208d838d0906a5d92b4bdca903104a6d0ad46eb4f2962a3447fc
Timestamp: 1712793118 Timestamp [UCT]: 2024-04-10 23:51:58 Age [y:d:h:m:s]: 01:066:22:42:46
Block: 997781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308759 RingCT/type: yes/0
Extra: 01a89a64118788208d838d0906a5d92b4bdca903104a6d0ad46eb4f2962a3447fc0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42533a8d302357a3a68f4d5c74195a49a10e07fc576d1ad048ab65a87a8e75ab 0.600000000000 1458215 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": 997791, "vin": [ { "gen": { "height": 997781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42533a8d302357a3a68f4d5c74195a49a10e07fc576d1ad048ab65a87a8e75ab" } } ], "extra": [ 1, 168, 154, 100, 17, 135, 136, 32, 141, 131, 141, 9, 6, 165, 217, 43, 75, 220, 169, 3, 16, 74, 109, 10, 212, 110, 180, 242, 150, 42, 52, 71, 252, 2, 17, 0, 0, 0, 5, 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