← previous blocknext block →recent activity
Analyzing
Block #103,211,305
28 transactions · 26 stateful · 2026-09-09 02:55:05 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,211,305 · 28 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
1w02w13w25w26w37w319w420w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac163e96…53ee
0x34b655…2a6f
14 touches
21 conflicts
0xb1856468…e84f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x4c7c2471…43d7
0x34b655…2a6f
6 touches
3 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
6 touches
3 conflicts
0x8f63f383…6eda
0x34b655…2a6f
4 touches
1 conflict
0x92b49f44…ee4f
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
21 conflicts on slot 0xac163e969a…fc53ee
Audit this contract →
← previous block·next block →recent activity