Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7071f57120c40530572d39ef26ffe89240bb125176163ec98c1a9de93846ccda

Tx prefix hash: a29e2cbb613c1146e5d95ffabe0130244c75c336fa3903930f0b4795ed5da51c
Tx public key: 7a683e2e8b2ad1ffba8f8d8a3d3d2fdf2d1a712e7b7d36871788096f0bbbaec0
Timestamp: 1638053301 Timestamp [UCT]: 2021-11-27 22:48:21 Age [y:d:h:m:s]: 02:346:05:25:25
Block: 383547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 765444 RingCT/type: yes/0
Extra: 017a683e2e8b2ad1ffba8f8d8a3d3d2fdf2d1a712e7b7d36871788096f0bbbaec0021100000024379224c2000000000000000000

1 output(s) for total of 32.897089137000 dcy

stealth address amount amount idx
00: 5b46cba7a6a9c93aa5ed01fd575894b4d47435a178462d11bb947e229fb3bae2 32.897089137000 774326 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": 383557, "vin": [ { "gen": { "height": 383547 } } ], "vout": [ { "amount": 32897089137, "target": { "key": "5b46cba7a6a9c93aa5ed01fd575894b4d47435a178462d11bb947e229fb3bae2" } } ], "extra": [ 1, 122, 104, 62, 46, 139, 42, 209, 255, 186, 143, 141, 138, 61, 61, 47, 223, 45, 26, 113, 46, 123, 125, 54, 135, 23, 136, 9, 111, 11, 187, 174, 192, 2, 17, 0, 0, 0, 36, 55, 146, 36, 194, 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