Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fed3be800c4aa10e6b01b8166a23f7e22eb9c9b82d15de35ac0129c1360020e

Tx prefix hash: 5eebe961e0f323249f0cd2d8a44b89672ebdc2df9be6dde86b25330399564f9f
Tx public key: 338d6424d387c76e92795c548e22d368e56b243138b4b18860e289ae1f47a2ae
Timestamp: 1737448959 Timestamp [UCT]: 2025-01-21 08:42:39 Age [y:d:h:m:s]: 00:147:10:34:43
Block: 1202022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105127 RingCT/type: yes/0
Extra: 01338d6424d387c76e92795c548e22d368e56b243138b4b18860e289ae1f47a2ae0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef08dd4bc00364eaa0f41ddeb937cbe8f3a6bd7a1c92d9055892ab5bde9e9113 0.600000000000 1688681 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": 1202032, "vin": [ { "gen": { "height": 1202022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef08dd4bc00364eaa0f41ddeb937cbe8f3a6bd7a1c92d9055892ab5bde9e9113" } } ], "extra": [ 1, 51, 141, 100, 36, 211, 135, 199, 110, 146, 121, 92, 84, 142, 34, 211, 104, 229, 107, 36, 49, 56, 180, 177, 136, 96, 226, 137, 174, 31, 71, 162, 174, 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