← previous blocknext block →recent activity

Analyzing

Block #111,839,386

22 transactions · 20 stateful · 2026-10-09 07:42:28 UTC

Parallelism

77/100

Blocked

40%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #111,839,386  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x51af0e92…4020

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xf9f8a78a…25f3

0x34b655…2a6f

4 touches
1 conflict

0x421b1a16…fe11

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x6ef772bc…7f64

0x34b655…2a6f

4 touches
1 conflict

0x7dbeccfc…8faf

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Perpl

6 conflicts on slot 0x51af0e92a5…be4020

← previous block·next block →recent activity