Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e85b7568e3eca52a52b77a99d57b4b7c738703f67d62cd7f8c8c03101485857

Tx prefix hash: 8f92fe836cad3a016ac952f7027abc3906ad0136ddb73c493f014caf7a584ac0
Tx public key: 8432717bbe0183d89f6ceb08eab17fd3c38873a8bd12eccb59c4e6f81f891982
Timestamp: 1719037319 Timestamp [UCT]: 2024-06-22 06:21:59 Age [y:d:h:m:s]: 00:292:02:01:45
Block: 1049559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208734 RingCT/type: yes/0
Extra: 018432717bbe0183d89f6ceb08eab17fd3c38873a8bd12eccb59c4e6f81f8919820211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9062846841832eb317940d8d3a2b6824b60ff14a6d1c7470ca6c0f0ac6168b58 0.600000000000 1519658 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": 1049569, "vin": [ { "gen": { "height": 1049559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9062846841832eb317940d8d3a2b6824b60ff14a6d1c7470ca6c0f0ac6168b58" } } ], "extra": [ 1, 132, 50, 113, 123, 190, 1, 131, 216, 159, 108, 235, 8, 234, 177, 127, 211, 195, 136, 115, 168, 189, 18, 236, 203, 89, 196, 230, 248, 31, 137, 25, 130, 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