← previous blocknext block →recent activity
Analyzing
Block #106,954,483
21 transactions · 20 stateful · 2026-09-22 05:41:58 UTC
Parallelism
76/100
Blocked
45%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,954,483 · 21 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
2w04w16w27w310w011w115w217w318w419w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9db7caf6…ccfc
0x34b655…2a6f
8 touches
6 conflicts
0xa4a1ecf7…9e63
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc53799eb…d928
0x34b655…2a6f
6 touches
3 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
6 touches
3 conflicts
0x9352dc74…6931
0x34b655…2a6f
4 touches
1 conflict
0x9600ce47…db97
0x34b655…2a6f
4 touches
1 conflict
0xa9a9d0e0…4087
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 0x9db7caf6e2…a9ccfc
Audit this contract →
← previous block·next block →recent activity