Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4659447be21036e817912646d11e2adbe0042ce912599f813a2e213cf76d5a4d

Tx prefix hash: c5eaa2f3d0bd31511004e7137bc080fed0e5af3e18870984e1c75aea791172d5
Tx public key: 1a370f3b9f220c79075dc12ff0a9bfd75a5b52deca91ef0bc2b5261a56e3db6a
Timestamp: 1737266732 Timestamp [UCT]: 2025-01-19 06:05:32 Age [y:d:h:m:s]: 00:108:13:26:27
Block: 1200513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77429 RingCT/type: yes/0
Extra: 011a370f3b9f220c79075dc12ff0a9bfd75a5b52deca91ef0bc2b5261a56e3db6a02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dedcd86118cc8339882b681100c81c1e38587f82347b38223d79c1a967a01f7 0.600000000000 1687158 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": 1200523, "vin": [ { "gen": { "height": 1200513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dedcd86118cc8339882b681100c81c1e38587f82347b38223d79c1a967a01f7" } } ], "extra": [ 1, 26, 55, 15, 59, 159, 34, 12, 121, 7, 93, 193, 47, 240, 169, 191, 215, 90, 91, 82, 222, 202, 145, 239, 11, 194, 181, 38, 26, 86, 227, 219, 106, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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