Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69108e17c4961827a87434c0f912310ccfa5d7e553f7297adda9872458c82bf7

Tx prefix hash: 57df1c63507e1c7666e950b11abaa091c1d84f93ffe781d4a93e2a9beb7ce1ed
Tx public key: d59ae019a5048aa32ac40da98557ec392ed9ab2d38e91ed4ba922a3c8d79eedd
Timestamp: 1696093351 Timestamp [UCT]: 2023-09-30 17:02:31 Age [y:d:h:m:s]: 01:191:03:11:14
Block: 859561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397645 RingCT/type: yes/0
Extra: 01d59ae019a5048aa32ac40da98557ec392ed9ab2d38e91ed4ba922a3c8d79eedd0211000000014b8f5122000000000000000000

1 output(s) for total of 0.870798413000 dcy

stealth address amount amount idx
00: dde9897bd919cb06b51c606a582ba76d8a7b2c201b6c6d456565d8e4e6c0be6e 0.870798413000 1313793 of 0

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": 859571, "vin": [ { "gen": { "height": 859561 } } ], "vout": [ { "amount": 870798413, "target": { "key": "dde9897bd919cb06b51c606a582ba76d8a7b2c201b6c6d456565d8e4e6c0be6e" } } ], "extra": [ 1, 213, 154, 224, 25, 165, 4, 138, 163, 42, 196, 13, 169, 133, 87, 236, 57, 46, 217, 171, 45, 56, 233, 30, 212, 186, 146, 42, 60, 141, 121, 238, 221, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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