Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6197cc7ba734b780fdd119bbe041a24eb3212366b113971a033633335399be97

Tx prefix hash: c67ca47327eb2d9f4583ae8f280a55599a5e1528f71ca1a7ff0465fcf1b6f309
Tx public key: b288178dcc421c9e3fdc62da092d38d2bd44f429749914a4f7db703d83c76e6f
Timestamp: 1710537523 Timestamp [UCT]: 2024-03-15 21:18:43 Age [y:d:h:m:s]: 01:046:13:11:21
Block: 979124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294247 RingCT/type: yes/0
Extra: 01b288178dcc421c9e3fdc62da092d38d2bd44f429749914a4f7db703d83c76e6f02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f2e70d705741764d159971a64a758ec5f450feebc38beaa7ba2a379cac777c1 0.600000000000 1439157 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": 979134, "vin": [ { "gen": { "height": 979124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f2e70d705741764d159971a64a758ec5f450feebc38beaa7ba2a379cac777c1" } } ], "extra": [ 1, 178, 136, 23, 141, 204, 66, 28, 158, 63, 220, 98, 218, 9, 45, 56, 210, 189, 68, 244, 41, 116, 153, 20, 164, 247, 219, 112, 61, 131, 199, 110, 111, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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