← previous blocknext block →recent activity
Analyzing
Block #106,916,503
23 transactions · 19 stateful · 2026-09-22 02:30:48 UTC
Parallelism
57/100
Blocked
58%
Avg conflicts / tx
1.39
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,916,503 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w510w611w712w813w922w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51087f5a…61f7
0x34b655…2a6f
12 touches
15 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
12 touches
15 conflicts
0x803d32b5…8094
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0xf782ee27…41cd
0x34b655…2a6f
10 touches
10 conflicts
0x91220b8f…7a06
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
15 conflicts on slot 0x51087f5abf…f061f7
Audit this contract →
← previous block·next block →recent activity