← previous blocknext block →recent activity
Analyzing
Block #104,167,068
12 transactions · 9 stateful · 2026-09-12 11:24:22 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,167,068 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9f0b0dc…4827
0x34b655…2a6f
4 touches
1 conflict
0xd0fd6c76…ddaf
0x34b655…2a6f
4 touches
1 conflict
0xf8cb14ea…b0eb
0x34b655…2a6f
4 touches
1 conflict
0x28ea43af…a9c1
0x34b655…2a6f
4 touches
1 conflict
0x0aa5e418…5d1d
0x34b655…2a6f
2 touches
0 conflicts
0x1294a92c…f91e
0x34b655…2a6f
2 touches
0 conflicts
0x16e75abd…f3ad
0x34b655…2a6f
2 touches
0 conflicts
0x4073f47e…39e6
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xb9f0b0dc52…ec4827
Audit this contract →
← previous block·next block →recent activity