Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8abdc2f0f011cb8a87a8a755e544b7876bea0c9cc29df1d34f5c2954f6bbd721

Tx prefix hash: e0dd04266c0699ec076235426670257189d22e0cc432c36f03a92e3249864427
Tx public key: c9d634f0f8a0f83312127ff47d0977fbf0c6d2762d3e8424d0cd716abb36af56
Timestamp: 1731230156 Timestamp [UCT]: 2024-11-10 09:15:56 Age [y:d:h:m:s]: 00:014:01:55:06
Block: 1150567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10078 RingCT/type: yes/0
Extra: 01c9d634f0f8a0f83312127ff47d0977fbf0c6d2762d3e8424d0cd716abb36af560211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5a9c75596ae99d790f1670d7a99f79a4f26ac1e17c0dedbb43eaffa4515bc03 0.600000000000 1635920 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": 1150577, "vin": [ { "gen": { "height": 1150567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5a9c75596ae99d790f1670d7a99f79a4f26ac1e17c0dedbb43eaffa4515bc03" } } ], "extra": [ 1, 201, 214, 52, 240, 248, 160, 248, 51, 18, 18, 127, 244, 125, 9, 119, 251, 240, 198, 210, 118, 45, 62, 132, 36, 208, 205, 113, 106, 187, 54, 175, 86, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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