Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0184ef9466712e3f85750b631ccb8faea027d31798595ada8fd1eeab9e91d7ba

Tx prefix hash: c54540034936a0279daf13eb8e9065f7f2503ceb7f84268bcef3a34695b92ef7
Tx public key: 00e9adb24f62f4ca1d6e9ab5a6786e9f2525568d04e12b3b232d7e0201a3e676
Timestamp: 1709515029 Timestamp [UCT]: 2024-03-04 01:17:09 Age [y:d:h:m:s]: 01:010:23:25:49
Block: 970634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268850 RingCT/type: yes/0
Extra: 0100e9adb24f62f4ca1d6e9ab5a6786e9f2525568d04e12b3b232d7e0201a3e6760211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10e5e89d5500ed84172aaef52a60a04edd7bab0ebef22c22a39120cd2f887ff8 0.600000000000 1430493 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": 970644, "vin": [ { "gen": { "height": 970634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10e5e89d5500ed84172aaef52a60a04edd7bab0ebef22c22a39120cd2f887ff8" } } ], "extra": [ 1, 0, 233, 173, 178, 79, 98, 244, 202, 29, 110, 154, 181, 166, 120, 110, 159, 37, 37, 86, 141, 4, 225, 43, 59, 35, 45, 126, 2, 1, 163, 230, 118, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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