Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 252f0a291c5173f822cb1ded4033d925a53c96f64700aef6ed1e1425aadb8aa9

Tx prefix hash: 163221ff6a903037f2a56fc024d9cb1f7e3a5c762c0ae1106635919abd149a7a
Tx public key: 3408211bad89ece9e214da5fdb054c32d55dcbe8f818bdde7dd409b26d6b8960
Timestamp: 1698184311 Timestamp [UCT]: 2023-10-24 21:51:51 Age [y:d:h:m:s]: 01:099:14:10:16
Block: 876909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332145 RingCT/type: yes/0
Extra: 013408211bad89ece9e214da5fdb054c32d55dcbe8f818bdde7dd409b26d6b8960021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.762845306000 dcy

stealth address amount amount idx
00: f0ede4e347d495e268e55ea5de1540df14121536e2b90d877a4e5ff5129aa55b 0.762845306000 1332257 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": 876919, "vin": [ { "gen": { "height": 876909 } } ], "vout": [ { "amount": 762845306, "target": { "key": "f0ede4e347d495e268e55ea5de1540df14121536e2b90d877a4e5ff5129aa55b" } } ], "extra": [ 1, 52, 8, 33, 27, 173, 137, 236, 233, 226, 20, 218, 95, 219, 5, 76, 50, 213, 93, 203, 232, 248, 24, 189, 222, 125, 212, 9, 178, 109, 107, 137, 96, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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