Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0c6525b55e85190ff3e40ca62f9cf2a966c320405be85cfafead8e39ef4b9f2

Tx prefix hash: 65617e0c0df51618ce1e43c9b2b359c28620671993e706aee2314b68e627bcbf
Tx public key: cd1b9320899d597fb49fb164185af8ceb962bef20a9c647b76439b81d176cdd4
Timestamp: 1740340395 Timestamp [UCT]: 2025-02-23 19:53:15 Age [y:d:h:m:s]: 00:226:09:25:51
Block: 1225717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159503 RingCT/type: yes/0
Extra: 01cd1b9320899d597fb49fb164185af8ceb962bef20a9c647b76439b81d176cdd40211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 660f2b40ce45ac67c4b849d7a85bca3caeabeaaaf7f14f052b6bcf417d31e6d3 0.600000000000 1712584 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": 1225727, "vin": [ { "gen": { "height": 1225717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "660f2b40ce45ac67c4b849d7a85bca3caeabeaaaf7f14f052b6bcf417d31e6d3" } } ], "extra": [ 1, 205, 27, 147, 32, 137, 157, 89, 127, 180, 159, 177, 100, 24, 90, 248, 206, 185, 98, 190, 242, 10, 156, 100, 123, 118, 67, 155, 129, 209, 118, 205, 212, 2, 17, 0, 0, 0, 1, 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