Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 914c55664b39c13e7ee7f273fe905923c7bea875685d40b1e4bd16e005eeac7c

Tx prefix hash: 5225321f936c49fc3ddcd351a0a7e8998e9615e1f7bec60b8f320f81999e3bf6
Tx public key: 91852371c70f1ea354ae3b3b3fa57d4eb1c874b9935a830aeb0a6cd2d0f083ea
Timestamp: 1720449327 Timestamp [UCT]: 2024-07-08 14:35:27 Age [y:d:h:m:s]: 00:200:09:59:03
Block: 1061287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143358 RingCT/type: yes/0
Extra: 0191852371c70f1ea354ae3b3b3fa57d4eb1c874b9935a830aeb0a6cd2d0f083ea021100000001c26d3a99000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcb93ac4d0627059b1d33f5a0ec91e33389eff0b70de33d5f3ce7cef48712197 0.600000000000 1531778 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": 1061297, "vin": [ { "gen": { "height": 1061287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcb93ac4d0627059b1d33f5a0ec91e33389eff0b70de33d5f3ce7cef48712197" } } ], "extra": [ 1, 145, 133, 35, 113, 199, 15, 30, 163, 84, 174, 59, 59, 63, 165, 125, 78, 177, 200, 116, 185, 147, 90, 131, 10, 235, 10, 108, 210, 208, 240, 131, 234, 2, 17, 0, 0, 0, 1, 194, 109, 58, 153, 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