Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6e9555da6b32abc22717bdc0488cc20cc2ccf38eb691f719e242febc2dea676

Tx prefix hash: 8d1051cef4cf3f521e21209887033947db056f7995de2aaab9602e2fe0e00d20
Tx public key: 5101f453fd79da4739b4eab7c9e4a2070ee4f878f4ef7172cfe56868ab14a5fd
Timestamp: 1701082131 Timestamp [UCT]: 2023-11-27 10:48:51 Age [y:d:h:m:s]: 01:171:03:50:53
Block: 900706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383530 RingCT/type: yes/0
Extra: 015101f453fd79da4739b4eab7c9e4a2070ee4f878f4ef7172cfe56868ab14a5fd02110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.636190388000 dcy

stealth address amount amount idx
00: a38ba8ec9e618e3347e10071f190aa583a6455d3837518238f3ebcf46a971278 0.636190388000 1357221 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": 900716, "vin": [ { "gen": { "height": 900706 } } ], "vout": [ { "amount": 636190388, "target": { "key": "a38ba8ec9e618e3347e10071f190aa583a6455d3837518238f3ebcf46a971278" } } ], "extra": [ 1, 81, 1, 244, 83, 253, 121, 218, 71, 57, 180, 234, 183, 201, 228, 162, 7, 14, 228, 248, 120, 244, 239, 113, 114, 207, 229, 104, 104, 171, 20, 165, 253, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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