Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 982ebe2f2624f609feff1d6431c2cc4bbb9108abb7433459d92d9c2b772f8f35

Tx prefix hash: 94ea9f6dd7bf8bcb1d83401f54126556cc4c334abcc84617408f7d529420b322
Tx public key: 1de4a09ddaafed21ddec1f79c886f27dc2bda80d0c88f5e9ce8fdd903f07dd84
Timestamp: 1729524017 Timestamp [UCT]: 2024-10-21 15:20:17 Age [y:d:h:m:s]: 00:155:19:52:24
Block: 1136476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111154 RingCT/type: yes/0
Extra: 011de4a09ddaafed21ddec1f79c886f27dc2bda80d0c88f5e9ce8fdd903f07dd840211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baee663f3837d3b967a57d984a3e6cb781e89198b02d79a39349f07f741411c1 0.600000000000 1619821 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": 1136486, "vin": [ { "gen": { "height": 1136476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baee663f3837d3b967a57d984a3e6cb781e89198b02d79a39349f07f741411c1" } } ], "extra": [ 1, 29, 228, 160, 157, 218, 175, 237, 33, 221, 236, 31, 121, 200, 134, 242, 125, 194, 189, 168, 13, 12, 136, 245, 233, 206, 143, 221, 144, 63, 7, 221, 132, 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