Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f404e1e38ca2a82ab0a49ab8f684850b1f396ee6f1a250f29c9e1716af00a15

Tx prefix hash: 9202839593a1d47f406d5004cf8ede5a71fe51c8aabe2001f5063c0b7d12556e
Tx public key: e0516af3e80728a1b70c2f256097e10624d3b86a7c21fe19d611041e938763bb
Timestamp: 1584506217 Timestamp [UCT]: 2020-03-18 04:36:57 Age [y:d:h:m:s]: 04:352:14:22:14
Block: 84551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147596 RingCT/type: yes/0
Extra: 01e0516af3e80728a1b70c2f256097e10624d3b86a7c21fe19d611041e938763bb02110000002848d4d863000000000000000000

1 output(s) for total of 321.994327939000 dcy

stealth address amount amount idx
00: 4135f60020888693b5b16f84769a312299a928029af49449d0333117304d3bec 321.994327939000 153223 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": 84561, "vin": [ { "gen": { "height": 84551 } } ], "vout": [ { "amount": 321994327939, "target": { "key": "4135f60020888693b5b16f84769a312299a928029af49449d0333117304d3bec" } } ], "extra": [ 1, 224, 81, 106, 243, 232, 7, 40, 161, 183, 12, 47, 37, 96, 151, 225, 6, 36, 211, 184, 106, 124, 33, 254, 25, 214, 17, 4, 30, 147, 135, 99, 187, 2, 17, 0, 0, 0, 40, 72, 212, 216, 99, 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