Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3cbef528bd8b0fa3cc34e9a47fa96c8ef3eb73000894001a237353486aa95f5

Tx prefix hash: 496e015e773c507de394d366dd8304ba293e451f3172537ad603b855cd8ab529
Tx public key: ade6107dc668afa08cbcdb62b08fdcddf6ff3d89e8c66be9b7f22b41d0efb69a
Timestamp: 1710637943 Timestamp [UCT]: 2024-03-17 01:12:23 Age [y:d:h:m:s]: 01:236:16:26:49
Block: 979962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427838 RingCT/type: yes/0
Extra: 01ade6107dc668afa08cbcdb62b08fdcddf6ff3d89e8c66be9b7f22b41d0efb69a0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11f0a3e5e5da436000a14da90e3d473adf127d75063b43e0a9c6baabcae9f11c 0.600000000000 1440019 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": 979972, "vin": [ { "gen": { "height": 979962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11f0a3e5e5da436000a14da90e3d473adf127d75063b43e0a9c6baabcae9f11c" } } ], "extra": [ 1, 173, 230, 16, 125, 198, 104, 175, 160, 140, 188, 219, 98, 176, 143, 220, 221, 246, 255, 61, 137, 232, 198, 107, 233, 183, 242, 43, 65, 208, 239, 182, 154, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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