← previous blocknext block →recent activity
Analyzing
Block #103,986,275
22 transactions · 21 stateful · 2026-09-11 20:04:41 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #103,986,275 · 22 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
1w06w19w010w112w213w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6dedaff6…161b
0x34b655…2a6f
16 touches
28 conflicts
0x1f396cee…862f
0x34b655…2a6f
16 touches
28 conflicts
0x898d9b8a…d1ef
0x34b655…2a6f
16 touches
28 conflicts
0x17b94c2f…869e
0x34b655…2a6f
16 touches
28 conflicts
0x52343e15…a8de
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
16 touches
28 conflicts
0xbeb8ca3a…a08c
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
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
28 conflicts on slot 0x6dedaff684…2d161b
Audit this contract →
← previous block·next block →recent activity