Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 120b1775b70907418c266ef73e35f91604b918159abdaf8409d4dc357cd1f846

Tx prefix hash: 46ee4aeefa61fe1c10db465468a0cae991d3e8af0fb0ab99486b5a563e886266
Tx public key: 9484a77de721ae1cdad5e1df97c2a6178b03d2f0bbd7b860d365740be2ebae84
Timestamp: 1720913789 Timestamp [UCT]: 2024-07-13 23:36:29 Age [y:d:h:m:s]: 00:278:18:05:10
Block: 1065143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199153 RingCT/type: yes/0
Extra: 019484a77de721ae1cdad5e1df97c2a6178b03d2f0bbd7b860d365740be2ebae8402110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b2a93e3191afde42850f7723b0a3600ed09c50595654004e6ebccea75208e92 0.600000000000 1535686 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": 1065153, "vin": [ { "gen": { "height": 1065143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b2a93e3191afde42850f7723b0a3600ed09c50595654004e6ebccea75208e92" } } ], "extra": [ 1, 148, 132, 167, 125, 231, 33, 174, 28, 218, 213, 225, 223, 151, 194, 166, 23, 139, 3, 210, 240, 187, 215, 184, 96, 211, 101, 116, 11, 226, 235, 174, 132, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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