Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56963c7a6fe4b67f7bf34b58f4dd26dd748c89fe4bf3ea183b1e734241171b66

Tx prefix hash: 061ea843c4709fc805c4eec024076601ce7e0489cae950f97916b007f67b0413
Tx public key: d938e4a37c6b5a41c7514b9e191e932e10a5271f24310e06328b214dacd65b36
Timestamp: 1710349740 Timestamp [UCT]: 2024-03-13 17:09:00 Age [y:d:h:m:s]: 01:034:12:55:33
Block: 977568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285665 RingCT/type: yes/0
Extra: 01d938e4a37c6b5a41c7514b9e191e932e10a5271f24310e06328b214dacd65b3602110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af586cf7030e178e6fc11124e856e127c95bf51dd2824dc790dd11f775993f1f 0.600000000000 1437571 of 15

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": 977578, "vin": [ { "gen": { "height": 977568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af586cf7030e178e6fc11124e856e127c95bf51dd2824dc790dd11f775993f1f" } } ], "extra": [ 1, 217, 56, 228, 163, 124, 107, 90, 65, 199, 81, 75, 158, 25, 30, 147, 46, 16, 165, 39, 31, 36, 49, 14, 6, 50, 139, 33, 77, 172, 214, 91, 54, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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