Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e73528322c537aec0e09eee79aa8dee28c353ad34fdfb56d0db96d6e37477412

Tx prefix hash: c21512de066a783e5443e0ba54d52e4ddfcef706f64b31fa8b621846f6e94b83
Tx public key: f2ffddc81e081fb59bc5e88314ab42d859b5d39d2899ccb01bf741424b3724c4
Timestamp: 1768007242 Timestamp [UCT]: 2026-01-10 01:07:22 Age [y:d:h:m:s]: 00:018:15:39:41
Block: 1452424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13168 RingCT/type: yes/0
Extra: 01f2ffddc81e081fb59bc5e88314ab42d859b5d39d2899ccb01bf741424b3724c4021100000002215bbf89000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7644ebc883e7ed991490a9b4448db37e4e7ce814f8e555905c7c439a79fd0bfc 0.600000000000 1941448 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": 1452434, "vin": [ { "gen": { "height": 1452424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7644ebc883e7ed991490a9b4448db37e4e7ce814f8e555905c7c439a79fd0bfc" } } ], "extra": [ 1, 242, 255, 221, 200, 30, 8, 31, 181, 155, 197, 232, 131, 20, 171, 66, 216, 89, 181, 211, 157, 40, 153, 204, 176, 27, 247, 65, 66, 75, 55, 36, 196, 2, 17, 0, 0, 0, 2, 33, 91, 191, 137, 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