Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 202b2df076a386c0764efdb03b8efe853c6d849caae27292b35d5e258e2b90cd

Tx prefix hash: cde5fccf0f159a95c6134888c0d62f9bf1cefcdd149ee6e4844e648f288a43b8
Tx public key: bdc3d5d1d55f2353d2a4eb6589f8ee5c5fe9d922a8f2a375b4756b5ea5b8f5e0
Timestamp: 1719193103 Timestamp [UCT]: 2024-06-24 01:38:23 Age [y:d:h:m:s]: 01:136:14:18:25
Block: 1050857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356175 RingCT/type: yes/0
Extra: 01bdc3d5d1d55f2353d2a4eb6589f8ee5c5fe9d922a8f2a375b4756b5ea5b8f5e002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 599e47e37aec519a767c4edf765d91fadb34e0ed9a50b894f9722d63602cdc8c 0.600000000000 1521032 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": 1050867, "vin": [ { "gen": { "height": 1050857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "599e47e37aec519a767c4edf765d91fadb34e0ed9a50b894f9722d63602cdc8c" } } ], "extra": [ 1, 189, 195, 213, 209, 213, 95, 35, 83, 210, 164, 235, 101, 137, 248, 238, 92, 95, 233, 217, 34, 168, 242, 163, 117, 180, 117, 107, 94, 165, 184, 245, 224, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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