Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 236e6b81cd026b4579798e7d47783dd704fb0d2f311976ec02e00b6bebb7cee5

Tx prefix hash: f159cbca5e1612d3f0ed4881df00d5c55f6ec5c30ba06e9d89feaf7025a88f58
Tx public key: b9f9427d210bb4fdcca0e978d4e20743d8d8bc367994bffe3677abf324f90960
Timestamp: 1726574732 Timestamp [UCT]: 2024-09-17 12:05:32 Age [y:d:h:m:s]: 01:052:22:07:46
Block: 1112062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296236 RingCT/type: yes/0
Extra: 01b9f9427d210bb4fdcca0e978d4e20743d8d8bc367994bffe3677abf324f90960021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02a10d311702664c79900672dc9106c63670bb28227c6f3043f77e388b8680c7 0.600000000000 1591251 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": 1112072, "vin": [ { "gen": { "height": 1112062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02a10d311702664c79900672dc9106c63670bb28227c6f3043f77e388b8680c7" } } ], "extra": [ 1, 185, 249, 66, 125, 33, 11, 180, 253, 204, 160, 233, 120, 212, 226, 7, 67, 216, 216, 188, 54, 121, 148, 191, 254, 54, 119, 171, 243, 36, 249, 9, 96, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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