Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 847515aa5e7a7947404e40aec1f8394ddd6501c52829351e88213302d3f128de

Tx prefix hash: 963c9b1aac27649f28cedd66a99ee13d0d2436777d48619069a34f6c9a73e352
Tx public key: a986634cf6d0e6ae9f9d4f5aa137ce4da429ad4b9cf30b9955d8656e4cd910e8
Timestamp: 1711139247 Timestamp [UCT]: 2024-03-22 20:27:27 Age [y:d:h:m:s]: 00:182:15:54:46
Block: 984121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130822 RingCT/type: yes/0
Extra: 01a986634cf6d0e6ae9f9d4f5aa137ce4da429ad4b9cf30b9955d8656e4cd910e802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95a51d235204adba9c1a31b043f92c82edcd25fe550ab4195991abd3167a9576 0.600000000000 1444276 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": 984131, "vin": [ { "gen": { "height": 984121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95a51d235204adba9c1a31b043f92c82edcd25fe550ab4195991abd3167a9576" } } ], "extra": [ 1, 169, 134, 99, 76, 246, 208, 230, 174, 159, 157, 79, 90, 161, 55, 206, 77, 164, 41, 173, 75, 156, 243, 11, 153, 85, 216, 101, 110, 76, 217, 16, 232, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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