← previous blocknext block →recent activity
Analyzing
Block #106,185,340
25 transactions · 23 stateful · 2026-09-19 13:09:48 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,185,340 · 25 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
1w02w13w04w15w16w27w08w115w016w117w018w119w220w321w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce4ecca8…166c
0x34b655…2a6f
8 touches
6 conflicts
0xc7e77378…f5a1
0x34b655…2a6f
8 touches
6 conflicts
0xc53799eb…d928
0x34b655…2a6f
8 touches
6 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xaa3b4402…74e6
0x34b655…2a6f
6 touches
3 conflicts
0x61037d3e…1885
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 0xce4ecca851…95166c
Audit this contract →
← previous block·next block →recent activity