Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b203f7ed7bc9f2bafa0204e850208f9aca502393ab63b9020cd56be4d4667bb9

Tx prefix hash: 0afc4c2899decda7714f66b82e05e5ab7e0b48243f70da399c56a433b3d7fb65
Tx public key: 00aa016619b6a230dfbf59f884d1f18de90b3b074b4d7b23fdb5289241c80def
Timestamp: 1706130248 Timestamp [UCT]: 2024-01-24 21:04:08 Age [y:d:h:m:s]: 01:081:17:16:49
Block: 942540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319501 RingCT/type: yes/0
Extra: 0100aa016619b6a230dfbf59f884d1f18de90b3b074b4d7b23fdb5289241c80def0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 184bc61b30ec8067a585eee5fbd56636c86ad0c68569b9b191100bb98eeed314 0.600000000000 1400714 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": 942550, "vin": [ { "gen": { "height": 942540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "184bc61b30ec8067a585eee5fbd56636c86ad0c68569b9b191100bb98eeed314" } } ], "extra": [ 1, 0, 170, 1, 102, 25, 182, 162, 48, 223, 191, 89, 248, 132, 209, 241, 141, 233, 11, 59, 7, 75, 77, 123, 35, 253, 181, 40, 146, 65, 200, 13, 239, 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