← previous blocknext block →recent activity
Analyzing
Block #106,955,518
14 transactions · 14 stateful · 2026-09-22 05:47:11 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,955,518 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8c615d4…5da3
0x34b655…2a6f
6 touches
3 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
6 touches
3 conflicts
0x4db105b4…056c
0x34b655…2a6f
4 touches
1 conflict
0x1c0bf87d…7fae
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xae798953…5e96
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
2 touches
0 conflicts
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
3 conflicts on slot 0xc8c615d41e…025da3
Audit this contract →
← previous block·next block →recent activity