Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d333b607956f20e560610401cedd5eabe043d649d1855f341a814b06d6929d2a

Tx prefix hash: d911065ae7f17fe104ab31491d6e724350b54c3fd70c09f01fedf1b7923bfb24
Tx public key: bd058615f22d99b2b052f048edc4291b0d3ad3012eb6a6220bced8784ba4d6f2
Timestamp: 1671956356 Timestamp [UCT]: 2022-12-25 08:19:16 Age [y:d:h:m:s]: 02:160:13:48:58
Block: 660125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 636496 RingCT/type: yes/0
Extra: 01bd058615f22d99b2b052f048edc4291b0d3ad3012eb6a6220bced8784ba4d6f2021100000005e6d27f9c000000000000000000

1 output(s) for total of 3.987785738000 dcy

stealth address amount amount idx
00: 0119e43c6383407419133bca927e6190158f0cca2f84698f62fc1a3ff266e0dc 3.987785738000 1100854 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": 660135, "vin": [ { "gen": { "height": 660125 } } ], "vout": [ { "amount": 3987785738, "target": { "key": "0119e43c6383407419133bca927e6190158f0cca2f84698f62fc1a3ff266e0dc" } } ], "extra": [ 1, 189, 5, 134, 21, 242, 45, 153, 178, 176, 82, 240, 72, 237, 196, 41, 27, 13, 58, 211, 1, 46, 182, 166, 34, 11, 206, 216, 120, 75, 164, 214, 242, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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