← previous blocknext block →recent activity
Analyzing
Block #104,161,178
20 transactions · 19 stateful · 2026-09-12 10:54:27 UTC
Parallelism
70/100
Blocked
26%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,161,178 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w111w212w313w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23f382f2…f742
0x34b655…2a6f
8 touches
6 conflicts
0x705a9a1a…db08
0x34b655…2a6f
8 touches
6 conflicts
0xec61dc1f…095f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x706c758c…2fdb
0x34b655…2a6f
6 touches
3 conflicts
0xf148676d…14d7
0x34b655…2a6f
4 touches
1 conflict
0x0172dba7…0333
0x34b655…2a6f
4 touches
1 conflict
0x5d6da397…6c5c
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
6 conflicts on slot 0x23f382f21f…8df742
Audit this contract →
← previous block·next block →recent activity