← previous blocknext block →recent activity
Analyzing
Block #104,197,230
23 transactions · 23 stateful · 2026-09-12 13:57:23 UTC
Parallelism
57/100
Blocked
52%
Avg conflicts / tx
1.87
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #104,197,230 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w27w112w314w415w516w517w618w720w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x86cea35b…bdff
0x34b655…2a6f
10 touches
10 conflicts
0x1408e7c7…f324
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xbce23dad…a8c0
0x34b655…2a6f
7 touches
6 conflicts
0x6636a104…d595
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity