Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ec33a9c3cfe245010da9adbcd1b7f101e3e4871ff555f128c321a83b5f6ab41

Tx prefix hash: 1b4d545d2301b57e4768714dba4355b1b4bf050d59e73f87fa592fa94651b069
Tx public key: b9814111b9592ede933d45117c10fcc9b1983ccbba870b5ce0d6e2f6302413e3
Timestamp: 1587355127 Timestamp [UCT]: 2020-04-20 03:58:47 Age [y:d:h:m:s]: 04:253:14:26:00
Block: 94410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1090772 RingCT/type: yes/0
Extra: 01b9814111b9592ede933d45117c10fcc9b1983ccbba870b5ce0d6e2f6302413e302110000013645705818000000000000000000

1 output(s) for total of 298.662879276000 dcy

stealth address amount amount idx
00: a01c27c6583b31cb9b86df71fdd7dc5884e6d815630fd07370e43a4f458141a7 298.662879276000 167902 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": 94420, "vin": [ { "gen": { "height": 94410 } } ], "vout": [ { "amount": 298662879276, "target": { "key": "a01c27c6583b31cb9b86df71fdd7dc5884e6d815630fd07370e43a4f458141a7" } } ], "extra": [ 1, 185, 129, 65, 17, 185, 89, 46, 222, 147, 61, 69, 17, 124, 16, 252, 201, 177, 152, 60, 203, 186, 135, 11, 92, 224, 214, 226, 246, 48, 36, 19, 227, 2, 17, 0, 0, 1, 54, 69, 112, 88, 24, 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