← previous blocknext block →recent activity
Analyzing
Block #106,931,039
31 transactions · 31 stateful · 2026-09-22 03:43:58 UTC
Parallelism
74/100
Blocked
55%
Avg conflicts / tx
1.81
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,931,039 · 31 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w010w011w112w213w314w315w216w320w423w124w125w526w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f41438c…0d4f
0x34b655…2a6f
16 touches
28 conflicts
0x85bfd0af…ce96
0x34b655…2a6f
14 touches
21 conflicts
0x810a3aa2…0227
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x61da5094…a3c9
0x34b655…2a6f
10 touches
10 conflicts
0x704a8131…bbe8
0x34b655…2a6f
8 touches
6 conflicts
0x70986451…c6bd
0x34b655…2a6f
8 touches
6 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x5f41438cce…d60d4f
Audit this contract →
← previous block·next block →recent activity