Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 426d2cf1508f64cf86d96003bccb2b5ba3ba4147e8ad89f38cb10819e27b71e6

Tx prefix hash: 5eafb0ca07707312906aca2263bc2afa73d098a2beb8eed0d3366111f48b59c3
Tx public key: f021a7c6a5a994f2dc260c001f241ec7c5f2f012bad3b3e31bbb3c9e7ac18c8d
Timestamp: 1738032452 Timestamp [UCT]: 2025-01-28 02:47:32 Age [y:d:h:m:s]: 00:140:11:39:40
Block: 1206664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100344 RingCT/type: yes/0
Extra: 01f021a7c6a5a994f2dc260c001f241ec7c5f2f012bad3b3e31bbb3c9e7ac18c8d0211000000151f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d80f81a2194b27d6df430f33ce817a7fa836c7b3f30c4ed9354797db9a3ee27 0.600000000000 1693375 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": 1206674, "vin": [ { "gen": { "height": 1206664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d80f81a2194b27d6df430f33ce817a7fa836c7b3f30c4ed9354797db9a3ee27" } } ], "extra": [ 1, 240, 33, 167, 198, 165, 169, 148, 242, 220, 38, 12, 0, 31, 36, 30, 199, 197, 242, 240, 18, 186, 211, 179, 227, 27, 187, 60, 158, 122, 193, 140, 141, 2, 17, 0, 0, 0, 21, 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