← previous blocknext block →recent activity
Analyzing
Block #104,202,027
26 transactions · 24 stateful · 2026-09-12 14:21:46 UTC
Parallelism
69/100
Blocked
63%
Avg conflicts / tx
1.62
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,202,027 · 26 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
1w02w13w24w35w06w17w38w29w210w311w214w415w516w319w621w725w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4eeb3ec…08f4
0x34b655…2a6f
12 touches
15 conflicts
0x4ccfe55c…de03
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x928d6b23…5373
0x1b6862…e19c
8 touches
6 conflicts
0x949fc5d9…55f3
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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
15 conflicts on slot 0xa4eeb3ec4a…0208f4
Audit this contract →
← previous block·next block →recent activity