Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0285b7300782ba430d2a405e773cd827a226e925242988c71ed18caea3a4e70b

Tx prefix hash: a3bd860768a23bd0805754b225f21d2c19e39e67eb11e2ed6d6dae4da79cce00
Tx public key: e8d8df48ef81c9f6fbd4e9028aa5da28bb065ad006e94e13cc6ed93f8134462c
Timestamp: 1583849956 Timestamp [UCT]: 2020-03-10 14:19:16 Age [y:d:h:m:s]: 04:261:10:35:14
Block: 79704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1082064 RingCT/type: yes/0
Extra: 01e8d8df48ef81c9f6fbd4e9028aa5da28bb065ad006e94e13cc6ed93f8134462c021100000003995a6b02000000000000000000

1 output(s) for total of 334.165552934000 dcy

stealth address amount amount idx
00: a1c1214b9ffd4c2e1da0fb5cae980952b712b5991b06ab5e40d25d9ee6f416bb 334.165552934000 145858 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": 79714, "vin": [ { "gen": { "height": 79704 } } ], "vout": [ { "amount": 334165552934, "target": { "key": "a1c1214b9ffd4c2e1da0fb5cae980952b712b5991b06ab5e40d25d9ee6f416bb" } } ], "extra": [ 1, 232, 216, 223, 72, 239, 129, 201, 246, 251, 212, 233, 2, 138, 165, 218, 40, 187, 6, 90, 208, 6, 233, 78, 19, 204, 110, 217, 63, 129, 52, 70, 44, 2, 17, 0, 0, 0, 3, 153, 90, 107, 2, 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