← previous blocknext block →recent activity
Analyzing
Block #104,200,262
21 transactions · 20 stateful · 2026-09-12 14:12:46 UTC
Parallelism
52/100
Blocked
50%
Avg conflicts / tx
2.05
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #104,200,262 · 21 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
1w02w13w04w15w26w38w49w514w615w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x1408e7c7…f324
0x34b655…2a6f
14 touches
21 conflicts
0xcc716e47…e524
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x948836ff…59ab
0x34b655…2a6f
10 touches
10 conflicts
0xe3b43222…522c
0x34b655…2a6f
8 touches
10 conflicts
0xc824469a…6426
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity