Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f68cf446ee49dc4ead54c3d25d16f8ead050a4234daa6d79fc12c9c00dfad324

Tx prefix hash: ef3b5800ec668bac0671ed1afc6b9e038569da923cfde258f1a5f9f6cc4be683
Tx public key: d714422192794f3ffe3d1bdc0d102ef243d9d215b334a3d302c8cd458765e344
Timestamp: 1727720084 Timestamp [UCT]: 2024-09-30 18:14:44 Age [y:d:h:m:s]: 01:037:16:48:47
Block: 1121562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285323 RingCT/type: yes/0
Extra: 01d714422192794f3ffe3d1bdc0d102ef243d9d215b334a3d302c8cd458765e344021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e72f791699e2a6f388793e0ab8641061072a61f4fb23b5a2a3cf113de799e4d 0.600000000000 1603851 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": 1121572, "vin": [ { "gen": { "height": 1121562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e72f791699e2a6f388793e0ab8641061072a61f4fb23b5a2a3cf113de799e4d" } } ], "extra": [ 1, 215, 20, 66, 33, 146, 121, 79, 63, 254, 61, 27, 220, 13, 16, 46, 242, 67, 217, 210, 21, 179, 52, 163, 211, 2, 200, 205, 69, 135, 101, 227, 68, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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