Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3193bc0d2ab88e37657cfc5777aaafff634e8a8bbcfb36ef0adbbe720baee21c

Tx prefix hash: 9a9577011244e71e23d86768855c26337d8454cd827a5e049ac4784fee14396e
Tx public key: d9c12f9b6341cc4729d324a3e247c6e99f8becc0a5e108e56222188f3cb83014
Timestamp: 1580570399 Timestamp [UCT]: 2020-02-01 15:19:59 Age [y:d:h:m:s]: 04:332:04:33:33
Block: 56665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128559 RingCT/type: yes/0
Extra: 01d9c12f9b6341cc4729d324a3e247c6e99f8becc0a5e108e56222188f3cb83014021100000006dcee4b4d000000000000000000

1 output(s) for total of 398.332879222000 dcy

stealth address amount amount idx
00: 5712a38616aacac3d6944232e9b58d117857f0edb855fd967a1586ba41da4a16 398.332879222000 104450 of 0

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": 56675, "vin": [ { "gen": { "height": 56665 } } ], "vout": [ { "amount": 398332879222, "target": { "key": "5712a38616aacac3d6944232e9b58d117857f0edb855fd967a1586ba41da4a16" } } ], "extra": [ 1, 217, 193, 47, 155, 99, 65, 204, 71, 41, 211, 36, 163, 226, 71, 198, 233, 159, 139, 236, 192, 165, 225, 8, 229, 98, 34, 24, 143, 60, 184, 48, 20, 2, 17, 0, 0, 0, 6, 220, 238, 75, 77, 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