Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71624ffa3b22ef4b863a63f44fff92315eeca0ab7d851fc4c6a80f6017cf79ba

Tx prefix hash: 24ef379e10119f3391d0704a885051f07132056bf69854f6855356637bd419df
Tx public key: 7b09b424210e118c67a73c2612d41e4c8f619e4fd88d5d3a6b0493dc3a9753f6
Timestamp: 1727170272 Timestamp [UCT]: 2024-09-24 09:31:12 Age [y:d:h:m:s]: 00:190:10:10:57
Block: 1117001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135900 RingCT/type: yes/0
Extra: 017b09b424210e118c67a73c2612d41e4c8f619e4fd88d5d3a6b0493dc3a9753f6021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 451d0602f2b8ba08844eb031a1d08b90d109e5886c9060bf59497a37a3842483 0.600000000000 1597680 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": 1117011, "vin": [ { "gen": { "height": 1117001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "451d0602f2b8ba08844eb031a1d08b90d109e5886c9060bf59497a37a3842483" } } ], "extra": [ 1, 123, 9, 180, 36, 33, 14, 17, 140, 103, 167, 60, 38, 18, 212, 30, 76, 143, 97, 158, 79, 216, 141, 93, 58, 107, 4, 147, 220, 58, 151, 83, 246, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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