Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b4d3f9f72cc02aeecf601f8746470376d0e5c06da6c9389e8be1d763d43476c

Tx prefix hash: 21cc3b2761653771133b931c0fce5db41bdf73483f7c0c5ba314a3ef0e2c84bb
Tx public key: ed35186348053b3e7d3a54e5e39eaf974f40bb934447faa6bcbd27cb01f42fd3
Timestamp: 1725074482 Timestamp [UCT]: 2024-08-31 03:21:22 Age [y:d:h:m:s]: 00:120:15:12:59
Block: 1099624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86276 RingCT/type: yes/0
Extra: 01ed35186348053b3e7d3a54e5e39eaf974f40bb934447faa6bcbd27cb01f42fd3021100000016e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30a96f1911ec9df197bdfbd09f9bfda6cd16af166056a4ef0be80190929afe96 0.600000000000 1575589 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": 1099634, "vin": [ { "gen": { "height": 1099624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30a96f1911ec9df197bdfbd09f9bfda6cd16af166056a4ef0be80190929afe96" } } ], "extra": [ 1, 237, 53, 24, 99, 72, 5, 59, 62, 125, 58, 84, 229, 227, 158, 175, 151, 79, 64, 187, 147, 68, 71, 250, 166, 188, 189, 39, 203, 1, 244, 47, 211, 2, 17, 0, 0, 0, 22, 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