← previous blocknext block →recent activity
Analyzing
Block #104,867,857
17 transactions · 15 stateful · 2026-09-14 22:36:30 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,867,857 · 17 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
3w04w05w17w08w19w210w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd7443f37…eb79
0x34b655…2a6f
12 touches
15 conflicts
0xf51ec09c…b4a9
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x6e0f1dd3…db06
0x34b655…2a6f
10 touches
10 conflicts
0x7250a4e7…cf29
0x34b655…2a6f
8 touches
6 conflicts
0x81d72b15…8f95
0x34b655…2a6f
6 touches
3 conflicts
0x62023181…811e
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity