Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff8528f964da05f1dbda810a454fc18dff4fb582f61440e452babeda9502f173

Tx prefix hash: 353391cf932072fb4dd3c895282e9a61941889ba49a9becc06bebbfcc2e4d1e0
Tx public key: 12ea77d09b6ea267cf05262ff7952d9294ed8f4afd583e5bb605c7e2431b3b1c
Timestamp: 1745100423 Timestamp [UCT]: 2025-04-19 22:07:03 Age [y:d:h:m:s]: 00:215:16:56:23
Block: 1265144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151876 RingCT/type: yes/0
Extra: 0112ea77d09b6ea267cf05262ff7952d9294ed8f4afd583e5bb605c7e2431b3b1c0211000000106c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d22dd68d850575328bf5e6e77e2ebcbcc29eb018e823cb0944a2e16785b23448 0.600000000000 1752347 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": 1265154, "vin": [ { "gen": { "height": 1265144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d22dd68d850575328bf5e6e77e2ebcbcc29eb018e823cb0944a2e16785b23448" } } ], "extra": [ 1, 18, 234, 119, 208, 155, 110, 162, 103, 207, 5, 38, 47, 247, 149, 45, 146, 148, 237, 143, 74, 253, 88, 62, 91, 182, 5, 199, 226, 67, 27, 59, 28, 2, 17, 0, 0, 0, 16, 108, 152, 170, 61, 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