← previous blocknext block →recent activity
Analyzing
Block #103,987,699
25 transactions · 23 stateful · 2026-09-11 20:11:54 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,987,699 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w08w19w210w311w412w513w623w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef048f92…572b
0x34b655…2a6f
14 touches
21 conflicts
0x077e96c0…df2c
0x34b655…2a6f
14 touches
21 conflicts
0x0942947e…563a
0x34b655…2a6f
14 touches
21 conflicts
0x45a7c210…d2d7
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x86cea35b…bdff
0x34b655…2a6f
14 touches
21 conflicts
0x8f63f383…6eda
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xef048f923c…1f572b
Audit this contract →
← previous block·next block →recent activity