Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 526c625e7d37b3c8e51f77915e5a2d020c2a8f851befc3641fc719bace745d08

Tx prefix hash: 563ce91b6cc3c5bc2d6315e46989f67e68ae25428259ff1b41b846750d99e6da
Tx public key: 55f60a23f8f3f1b097ad45678efc2f2889019c258d9d69553d67cbd858efa255
Timestamp: 1709933970 Timestamp [UCT]: 2024-03-08 21:39:30 Age [y:d:h:m:s]: 01:250:23:00:53
Block: 974107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438086 RingCT/type: yes/0
Extra: 0155f60a23f8f3f1b097ad45678efc2f2889019c258d9d69553d67cbd858efa2550211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5da77424236e5d760dba96509887d56d84c52c140c33192be4655178b0fb8be 0.600000000000 1434056 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": 974117, "vin": [ { "gen": { "height": 974107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5da77424236e5d760dba96509887d56d84c52c140c33192be4655178b0fb8be" } } ], "extra": [ 1, 85, 246, 10, 35, 248, 243, 241, 176, 151, 173, 69, 103, 142, 252, 47, 40, 137, 1, 156, 37, 141, 157, 105, 85, 61, 103, 203, 216, 88, 239, 162, 85, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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