← previous blocknext block →recent activity
Analyzing
Block #104,321,253
29 transactions · 29 stateful · 2026-09-13 00:26:36 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,321,253 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w27w08w116w018w119w221w322w023w424w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xa4e9800f…4ab1
0x34b655…2a6f
6 touches
3 conflicts
0x64d353bf…54ec
0x34b655…2a6f
4 touches
1 conflict
0x714420ba…96c5
0x34b655…2a6f
4 touches
1 conflict
0x9084429b…a7f8
0x34b655…2a6f
4 touches
1 conflict
0xb00be527…3e3a
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity