Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e706cbe09e86b5ef350bc7135d1f7deaf4afa34ddb2115402709294ad5a4bd9

Tx prefix hash: aea4c86fb21ae68dd330fff52b60f76c0c618b8b33f4df0cd006c19a95322402
Tx public key: c7ef0c197ad3201b9c0aea65565cf4fe51630fed40aba49359ab549fcae9f3c6
Timestamp: 1740616909 Timestamp [UCT]: 2025-02-27 00:41:49 Age [y:d:h:m:s]: 00:260:16:04:04
Block: 1228005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184064 RingCT/type: yes/0
Extra: 01c7ef0c197ad3201b9c0aea65565cf4fe51630fed40aba49359ab549fcae9f3c602110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c41d8ef0b2582855bdaf9f0cd45b4d1943676f0ccd18d76e162bda9d6a39895c 0.600000000000 1714882 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": 1228015, "vin": [ { "gen": { "height": 1228005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c41d8ef0b2582855bdaf9f0cd45b4d1943676f0ccd18d76e162bda9d6a39895c" } } ], "extra": [ 1, 199, 239, 12, 25, 122, 211, 32, 27, 156, 10, 234, 101, 86, 92, 244, 254, 81, 99, 15, 237, 64, 171, 164, 147, 89, 171, 84, 159, 202, 233, 243, 198, 2, 17, 0, 0, 0, 11, 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