← previous blocknext block →recent activity
Analyzing
Block #104,149,200
33 transactions · 27 stateful · 2026-09-12 09:53:35 UTC
Parallelism
70/100
Blocked
59%
Avg conflicts / tx
1.76
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #104,149,200 · 33 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
1w02w13w24w06w19w210w312w216w321w222w423w524w625w726w828w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x705a9a1a…db08
0x34b655…2a6f
18 touches
36 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0x75e22f9e…38e1
0x34b655…2a6f
12 touches
15 conflicts
0xf1352320…c9c3
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6426
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x705a9a1af8…69db08
Audit this contract →
← previous block·next block →recent activity