← previous blocknext block →recent activity
Analyzing
Block #106,952,801
14 transactions · 14 stateful · 2026-09-22 05:33:30 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,952,801 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w410w511w012w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea79e6d3…68ad
0x34b655…2a6f
8 touches
6 conflicts
0x19a2ed0b…e295
0x34b655…2a6f
8 touches
6 conflicts
0xc4c059d8…185d
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x3b948d19…8c39
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0x214f3b5e…dd2e
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 0xea79e6d350…ec68ad
Audit this contract →
← previous block·next block →recent activity