Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60cf593d9d499ce84d957e64f8b69161afb7e4b1bb7545ba5cc3d9b28b90a060

Tx prefix hash: 5033d422cc54abd68db43f255f219aea9feb5683c04093969e7215491fbe56a9
Tx public key: d2a9de634072fbb2aa0279145da394fc2835c9dc4a7d344de9350e22e2d8a024
Timestamp: 1740557237 Timestamp [UCT]: 2025-02-26 08:07:17 Age [y:d:h:m:s]: 00:313:12:51:25
Block: 1227519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221929 RingCT/type: yes/0
Extra: 01d2a9de634072fbb2aa0279145da394fc2835c9dc4a7d344de9350e22e2d8a0240211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 546e257197b185bffb95bc34bdba904c5cbf9da8daf40957485d56476f212cfa 0.600000000000 1714392 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": 1227529, "vin": [ { "gen": { "height": 1227519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "546e257197b185bffb95bc34bdba904c5cbf9da8daf40957485d56476f212cfa" } } ], "extra": [ 1, 210, 169, 222, 99, 64, 114, 251, 178, 170, 2, 121, 20, 93, 163, 148, 252, 40, 53, 201, 220, 74, 125, 52, 77, 233, 53, 14, 34, 226, 216, 160, 36, 2, 17, 0, 0, 0, 2, 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