Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50c439948e966a4f7443926aa1d252b66d7a89d3802cf1e9521eec391e593e80

Tx prefix hash: 24e5703640cefc7975a3bc99d57545851c7042ee48f74102d68508a3d6f6a1b5
Tx public key: 2fcbe85ac51351763fe0d406a4c18cb312514b37a791a165f1a2e4cbcf80279a
Timestamp: 1713744136 Timestamp [UCT]: 2024-04-22 00:02:16 Age [y:d:h:m:s]: 00:248:07:48:37
Block: 1005682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177770 RingCT/type: yes/0
Extra: 012fcbe85ac51351763fe0d406a4c18cb312514b37a791a165f1a2e4cbcf80279a0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b263c810824fb5dde0d5e5a4215acc63b794e54bb28bdbf03c63bdb797e7fbb 0.600000000000 1466452 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": 1005692, "vin": [ { "gen": { "height": 1005682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b263c810824fb5dde0d5e5a4215acc63b794e54bb28bdbf03c63bdb797e7fbb" } } ], "extra": [ 1, 47, 203, 232, 90, 197, 19, 81, 118, 63, 224, 212, 6, 164, 193, 140, 179, 18, 81, 75, 55, 167, 145, 161, 101, 241, 162, 228, 203, 207, 128, 39, 154, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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