← previous blocknext block →recent activity
Analyzing
Block #103,994,162
18 transactions · 18 stateful · 2026-09-11 20:44:42 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #103,994,162 · 18 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
1w02w03w04w15w26w07w110w311w112w313w114w115w417w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x141c6088…bb16
0x34b655…2a6f
10 touches
10 conflicts
0x4ccfe55c…de03
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x86cea35b…bdff
0x34b655…2a6f
6 touches
3 conflicts
0xe884e676…93a1
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb6ed530c…d450
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 0x141c6088c5…a3bb16
Audit this contract →
← previous block·next block →recent activity