Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3697f082ef56644826752dd627258652ad38b6774930c7a066c692f90e79569e

Tx prefix hash: 5b285f644e81cbe41343ef7429083fa16fefe78e255a7bb3c111df964062e47d
Tx public key: 1d6d2794c03642bb3addc59692a5cb7970e9d34aa51c6c04d1274474cc4eb2b5
Timestamp: 1737710122 Timestamp [UCT]: 2025-01-24 09:15:22 Age [y:d:h:m:s]: 00:144:17:28:24
Block: 1204184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103173 RingCT/type: yes/0
Extra: 011d6d2794c03642bb3addc59692a5cb7970e9d34aa51c6c04d1274474cc4eb2b5021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0283a8064e677413f45d21a1c4563aac63681fe5e0e3ef01b78b6d9d35a69a43 0.600000000000 1690869 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": 1204194, "vin": [ { "gen": { "height": 1204184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0283a8064e677413f45d21a1c4563aac63681fe5e0e3ef01b78b6d9d35a69a43" } } ], "extra": [ 1, 29, 109, 39, 148, 192, 54, 66, 187, 58, 221, 197, 150, 146, 165, 203, 121, 112, 233, 211, 74, 165, 28, 108, 4, 209, 39, 68, 116, 204, 78, 178, 181, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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