← previous blocknext block →recent activity
Analyzing
Block #106,944,480
20 transactions · 20 stateful · 2026-09-22 04:51:37 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,944,480 · 20 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
2w03w04w05w16w07w110w113w114w115w216w317w419w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f684419…5b5e
0x34b655…2a6f
10 touches
10 conflicts
0x5fad6fee…7714
0x34b655…2a6f
8 touches
6 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x704a8131…bbe8
0x34b655…2a6f
6 touches
3 conflicts
0x155e52ca…fac7
0x34b655…2a6f
6 touches
3 conflicts
0x47e004fe…ee14
0x34b655…2a6f
6 touches
3 conflicts
0xbdfd3604…cc6c
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
10 conflicts on slot 0x6f68441920…b95b5e
Audit this contract →
← previous block·next block →recent activity