← previous blocknext block →recent activity
Analyzing
Block #103,994,557
11 transactions · 11 stateful · 2026-09-11 20:46:43 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,994,557 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w17w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f54b878…6aaa
0x34b655…2a6f
4 touches
1 conflict
0x79b42917…bcb4
0x34b655…2a6f
4 touches
1 conflict
0xc2eff740…b10d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x4ccfe55c…de03
0x34b655…2a6f
4 touches
1 conflict
0xb839a1e8…22b3
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
1 conflict on slot 0x4f54b8789f…976aaa
Audit this contract →
← previous block·next block →recent activity