Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ad0ca86aecf21fa9fd726b4177a0996352a627a8dd9cadf789432808494494f

Tx prefix hash: 97d69c21f1bcc1c6483cadadbf55cc6bc2a68c63ea0e0a8e492e98b60a940f8a
Tx public key: 2203aea2ce79fe8cfcdd8576f756ac0dc5173c8c8a100bad8244e4b7aac2182e
Timestamp: 1583081305 Timestamp [UCT]: 2020-03-01 16:48:25 Age [y:d:h:m:s]: 05:047:11:21:25
Block: 74649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1188519 RingCT/type: yes/0
Extra: 012203aea2ce79fe8cfcdd8576f756ac0dc5173c8c8a100bad8244e4b7aac2182e0211000000078a2ee0d9000000000000000000

1 output(s) for total of 347.262328113000 dcy

stealth address amount amount idx
00: 50250a1d65ea3d2ff3dd8be6b69e26d17499ef1a79f446d669da713d620c32aa 347.262328113000 138097 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": 74659, "vin": [ { "gen": { "height": 74649 } } ], "vout": [ { "amount": 347262328113, "target": { "key": "50250a1d65ea3d2ff3dd8be6b69e26d17499ef1a79f446d669da713d620c32aa" } } ], "extra": [ 1, 34, 3, 174, 162, 206, 121, 254, 140, 252, 221, 133, 118, 247, 86, 172, 13, 197, 23, 60, 140, 138, 16, 11, 173, 130, 68, 228, 183, 170, 194, 24, 46, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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