Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b0e8054f99b93ffdbfc1fe541da284d6a73a12248898d20a89c8c24951e510b

Tx prefix hash: b508976f4c9e4037330ec42956f85f7e69401baa4c2d3d02ea970803c1daac2a
Tx public key: aef23969fb3c396fac3ad25b558c6709b1377f1c33049c12ce8b85db77ab9f4a
Timestamp: 1581904559 Timestamp [UCT]: 2020-02-17 01:55:59 Age [y:d:h:m:s]: 04:277:22:57:01
Block: 66402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1091079 RingCT/type: yes/0
Extra: 01aef23969fb3c396fac3ad25b558c6709b1377f1c33049c12ce8b85db77ab9f4a0211000000017adf42d3000000000000000000

1 output(s) for total of 369.814059612000 dcy

stealth address amount amount idx
00: a3305fd47fe87861eceb8e7182dbfe0ccef8f12b9aafd78b3d3850a6cd7fce6b 369.814059612000 122331 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": 66412, "vin": [ { "gen": { "height": 66402 } } ], "vout": [ { "amount": 369814059612, "target": { "key": "a3305fd47fe87861eceb8e7182dbfe0ccef8f12b9aafd78b3d3850a6cd7fce6b" } } ], "extra": [ 1, 174, 242, 57, 105, 251, 60, 57, 111, 172, 58, 210, 91, 85, 140, 103, 9, 177, 55, 127, 28, 51, 4, 156, 18, 206, 139, 133, 219, 119, 171, 159, 74, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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