Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 766b863ba9114d27d8ec93ed9d2670c66bdcb3d0dfb6411671a6e77124a5c990

Tx prefix hash: 4e638907760160205f8f261d9fe69096e4e231c098f073f95dcbc09b1252a33c
Tx public key: 7986ef97e773e271002c84e7731fefa512e1557e331014a1da6298427f091e4f
Timestamp: 1732192058 Timestamp [UCT]: 2024-11-21 12:27:38 Age [y:d:h:m:s]: 00:120:04:48:06
Block: 1158528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85730 RingCT/type: yes/0
Extra: 017986ef97e773e271002c84e7731fefa512e1557e331014a1da6298427f091e4f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c0cdad0efae3fe66bf920a08f66f2055b5d41e55cb308339988f3326649d81b 0.600000000000 1644157 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": 1158538, "vin": [ { "gen": { "height": 1158528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c0cdad0efae3fe66bf920a08f66f2055b5d41e55cb308339988f3326649d81b" } } ], "extra": [ 1, 121, 134, 239, 151, 231, 115, 226, 113, 0, 44, 132, 231, 115, 31, 239, 165, 18, 225, 85, 126, 51, 16, 20, 161, 218, 98, 152, 66, 127, 9, 30, 79, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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