Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1ea19d023e48eba36826d98835f46f737c8a49ea54e8f55360ccf7c7b975946

Tx prefix hash: 92956d338ec8564e5e4c31c92e44aa1853a5fb96e287c13ea7e14bee5f641685
Tx public key: 252ba39ef18963686b3b28506a0797548a42d5ae37e484e856c37957d42b16a7
Timestamp: 1717222685 Timestamp [UCT]: 2024-06-01 06:18:05 Age [y:d:h:m:s]: 00:310:19:17:21
Block: 1034536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222107 RingCT/type: yes/0
Extra: 01252ba39ef18963686b3b28506a0797548a42d5ae37e484e856c37957d42b16a7021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd86bb76ed234c00e9d08c1b1cb5fce608476dfd5cb5571d4e9f10b12973f903 0.600000000000 1503049 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": 1034546, "vin": [ { "gen": { "height": 1034536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd86bb76ed234c00e9d08c1b1cb5fce608476dfd5cb5571d4e9f10b12973f903" } } ], "extra": [ 1, 37, 43, 163, 158, 241, 137, 99, 104, 107, 59, 40, 80, 106, 7, 151, 84, 138, 66, 213, 174, 55, 228, 132, 232, 86, 195, 121, 87, 212, 43, 22, 167, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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