← previous blocknext block →recent activity
Analyzing
Block #104,158,429
18 transactions · 15 stateful · 2026-09-12 10:40:32 UTC
Parallelism
56/100
Blocked
60%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,158,429 · 18 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
1w02w13w05w26w310w411w513w615w116w717w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecea23db…7fb9
0x34b655…2a6f
12 touches
15 conflicts
0x1408e7c7…f324
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x07487c88…d403
0x34b655…2a6f
8 touches
6 conflicts
0xf72228f6…970c
0x34b655…2a6f
6 touches
3 conflicts
0x3accf018…2e8b
0x34b655…2a6f
6 touches
3 conflicts
0x800fe693…d09d
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
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
15 conflicts on slot 0xecea23db30…c07fb9
Audit this contract →
← previous block·next block →recent activity