Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 561dae8451edea9537e71301c96f9b1790a726f6d4498bab60fd53e7cb427fe6

Tx prefix hash: 45867fc6e88ecd53cfc245fcfd982ca9f28734c08f0ea9177463512d4dc52677
Tx public key: 2b3affad816754567b9275a319a1bfecf1b12e4684d0fc766fd9ac0b292fde1b
Timestamp: 1703650447 Timestamp [UCT]: 2023-12-27 04:14:07 Age [y:d:h:m:s]: 01:317:03:43:33
Block: 922009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485506 RingCT/type: yes/0
Extra: 012b3affad816754567b9275a319a1bfecf1b12e4684d0fc766fd9ac0b292fde1b02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6a0f7b0892d7ede664eb8375e502197cfb564d7d40e7df8ff7be0a452ddc946 0.600000000000 1379703 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": 922019, "vin": [ { "gen": { "height": 922009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6a0f7b0892d7ede664eb8375e502197cfb564d7d40e7df8ff7be0a452ddc946" } } ], "extra": [ 1, 43, 58, 255, 173, 129, 103, 84, 86, 123, 146, 117, 163, 25, 161, 191, 236, 241, 177, 46, 70, 132, 208, 252, 118, 111, 217, 172, 11, 41, 47, 222, 27, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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