Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83aaf51ff4c488e9c09164fe483639337270a1c8385640ef86f3c50ae3e36152

Tx prefix hash: 8a2b54e65a39ed5ff9ad88b200a97f30109d5641cafbd7ce32d78eeb96644278
Tx public key: c9787db7ba7570e702c8c76efd1280965fb60ee4b46d7ca2baf8cd472418f0cb
Timestamp: 1724450656 Timestamp [UCT]: 2024-08-23 22:04:16 Age [y:d:h:m:s]: 00:228:01:32:13
Block: 1094467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162841 RingCT/type: yes/0
Extra: 01c9787db7ba7570e702c8c76efd1280965fb60ee4b46d7ca2baf8cd472418f0cb021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c33d8b470be0052d35aecf45467b863d0149bbf9c1a9aa62b840a40263f1b2d 0.600000000000 1569584 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": 1094477, "vin": [ { "gen": { "height": 1094467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c33d8b470be0052d35aecf45467b863d0149bbf9c1a9aa62b840a40263f1b2d" } } ], "extra": [ 1, 201, 120, 125, 183, 186, 117, 112, 231, 2, 200, 199, 110, 253, 18, 128, 150, 95, 182, 14, 228, 180, 109, 124, 162, 186, 248, 205, 71, 36, 24, 240, 203, 2, 17, 0, 0, 0, 9, 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