Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1d0904153723adc24a3d75eee0438cb87562600174883be42b331845b401e99

Tx prefix hash: dacc39f65e882d7730df2a86d96c354b1172172594b2d48c0a320abf24b1f2a3
Tx public key: 2eb2b3ce81313f7ca4b800df6a0dd3bb39af5261a505d47f0da07a81039c21ea
Timestamp: 1638366049 Timestamp [UCT]: 2021-12-01 13:40:49 Age [y:d:h:m:s]: 03:001:09:24:45
Block: 386125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 779891 RingCT/type: yes/0
Extra: 012eb2b3ce81313f7ca4b800df6a0dd3bb39af5261a505d47f0da07a81039c21ea021100000010f6cc1430000000000000000000

1 output(s) for total of 32.255810474000 dcy

stealth address amount amount idx
00: b67a3a4b3cf71d8e0a84fa37f0c593ca2e890569dc07732139203737dee16fd1 32.255810474000 779070 of 0

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": 386135, "vin": [ { "gen": { "height": 386125 } } ], "vout": [ { "amount": 32255810474, "target": { "key": "b67a3a4b3cf71d8e0a84fa37f0c593ca2e890569dc07732139203737dee16fd1" } } ], "extra": [ 1, 46, 178, 179, 206, 129, 49, 63, 124, 164, 184, 0, 223, 106, 13, 211, 187, 57, 175, 82, 97, 165, 5, 212, 127, 13, 160, 122, 129, 3, 156, 33, 234, 2, 17, 0, 0, 0, 16, 246, 204, 20, 48, 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