Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f79d94c92ce02cbbb550ec0677580946559663c227b7123a0cb6580117e071d9

Tx prefix hash: d0d5c8fad553186afc7ad3e874f46a7321f0e4c0200169801d2f7d0b59fde412
Tx public key: 2029c6664b1a9c99339d10154727ecc78c82ce3c090e98ed9d1dac001284c5fa
Timestamp: 1735243859 Timestamp [UCT]: 2024-12-26 20:10:59 Age [y:d:h:m:s]: 00:173:06:28:18
Block: 1183810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123547 RingCT/type: yes/0
Extra: 012029c6664b1a9c99339d10154727ecc78c82ce3c090e98ed9d1dac001284c5fa0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8533a827cdbc950d927eb0ddf3df3a5e09e81ef5f139a5f1b5e74d8af597c053 0.600000000000 1670259 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": 1183820, "vin": [ { "gen": { "height": 1183810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8533a827cdbc950d927eb0ddf3df3a5e09e81ef5f139a5f1b5e74d8af597c053" } } ], "extra": [ 1, 32, 41, 198, 102, 75, 26, 156, 153, 51, 157, 16, 21, 71, 39, 236, 199, 140, 130, 206, 60, 9, 14, 152, 237, 157, 29, 172, 0, 18, 132, 197, 250, 2, 17, 0, 0, 0, 7, 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