Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc2a8998ff9ad3843c043d4d2face182fa9d0efc1309e7b6a905932edd2584a6

Tx prefix hash: bcb01fa25891b29afa8ea54a5047467a2b73da27db1e314393bf5848b15614dc
Tx public key: c2d342ccd320eb22786dfe5ad8432e7ff02e53642ea157e3ad260f23d5ad5b4c
Timestamp: 1733058799 Timestamp [UCT]: 2024-12-01 13:13:19 Age [y:d:h:m:s]: 00:116:12:27:52
Block: 1165722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83073 RingCT/type: yes/0
Extra: 01c2d342ccd320eb22786dfe5ad8432e7ff02e53642ea157e3ad260f23d5ad5b4c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 490511407f7b1013a8503f1cf1b192f95ebc0bc4d7dd26e1e8049e5afe50b759 0.600000000000 1651397 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": 1165732, "vin": [ { "gen": { "height": 1165722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "490511407f7b1013a8503f1cf1b192f95ebc0bc4d7dd26e1e8049e5afe50b759" } } ], "extra": [ 1, 194, 211, 66, 204, 211, 32, 235, 34, 120, 109, 254, 90, 216, 67, 46, 127, 240, 46, 83, 100, 46, 161, 87, 227, 173, 38, 15, 35, 213, 173, 91, 76, 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