Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06f01bd20933d71f63a15e4ff93103b73f2bb602ae3afb5b871dd1968c2bd3a5

Tx prefix hash: 5b1cdc7b690d5d1a4337f4b8f73a80a060333583524199ea53e05bc526aba791
Tx public key: a968710b8dc80db65837c7953017eb89e3c0f962ccb0dc8f40770d6cdcfb8a5b
Timestamp: 1581505710 Timestamp [UCT]: 2020-02-12 11:08:30 Age [y:d:h:m:s]: 05:018:05:43:34
Block: 63360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1165855 RingCT/type: yes/0
Extra: 01a968710b8dc80db65837c7953017eb89e3c0f962ccb0dc8f40770d6cdcfb8a5b02110000001b4943cd9f000000000000000000

1 output(s) for total of 378.497339743000 dcy

stealth address amount amount idx
00: 229ed0f63869cebe1f54f492696aa21cd6c24697bc6b8aed6c2e0ff2bd80872d 378.497339743000 116848 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": 63370, "vin": [ { "gen": { "height": 63360 } } ], "vout": [ { "amount": 378497339743, "target": { "key": "229ed0f63869cebe1f54f492696aa21cd6c24697bc6b8aed6c2e0ff2bd80872d" } } ], "extra": [ 1, 169, 104, 113, 11, 141, 200, 13, 182, 88, 55, 199, 149, 48, 23, 235, 137, 227, 192, 249, 98, 204, 176, 220, 143, 64, 119, 13, 108, 220, 251, 138, 91, 2, 17, 0, 0, 0, 27, 73, 67, 205, 159, 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