← previous blocknext block →recent activity
Analyzing
Block #106,198,653
20 transactions · 19 stateful · 2026-09-19 14:16:48 UTC
Parallelism
80/100
Blocked
26%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,198,653 · 20 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
1w06w08w19w212w013w116w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x708d7a74…09e3
0x34b655…2a6f
6 touches
3 conflicts
0xcfe180d7…b5a4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x86fe4251…6ad7
0x34b655…2a6f
4 touches
1 conflict
0x8765edd1…a7d5
0x34b655…2a6f
4 touches
1 conflict
0x98663459…4dff
0x34b655…2a6f
4 touches
1 conflict
0x98a224e3…70e8
0x34b655…2a6f
4 touches
1 conflict
0xc102b2b7…57a2
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
3 conflicts on slot 0x708d7a74a7…5d09e3
Audit this contract →
← previous block·next block →recent activity