Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19f4257b47d53abeeff8539e5e1b7b9d4b7f00a34ea5d861eeeef6fad9119f5a

Tx prefix hash: fa4f1ac86669f7fde87d03ffd75776f4d75f70eb14e25a4478a258d4d708944e
Tx public key: cc64d5282f4dd26d0113da2013aa981e1daa89ae192b6f04ec691185af906f21
Timestamp: 1706425649 Timestamp [UCT]: 2024-01-28 07:07:29 Age [y:d:h:m:s]: 01:087:12:17:29
Block: 944990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323646 RingCT/type: yes/0
Extra: 01cc64d5282f4dd26d0113da2013aa981e1daa89ae192b6f04ec691185af906f2102110000000652d47e94000000000000000000

1 output(s) for total of 0.600060000000 dcy

stealth address amount amount idx
00: 8d3009c50915e44ca7d8f89047acf0d23526eec82653982b6db64f5b743e1867 0.600060000000 1403296 of 0

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": 945000, "vin": [ { "gen": { "height": 944990 } } ], "vout": [ { "amount": 600060000, "target": { "key": "8d3009c50915e44ca7d8f89047acf0d23526eec82653982b6db64f5b743e1867" } } ], "extra": [ 1, 204, 100, 213, 40, 47, 77, 210, 109, 1, 19, 218, 32, 19, 170, 152, 30, 29, 170, 137, 174, 25, 43, 111, 4, 236, 105, 17, 133, 175, 144, 111, 33, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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