← previous blocknext block →recent activity
Analyzing
Block #102,210,046
21 transactions · 18 stateful · 2026-09-05 14:36:38 UTC
Parallelism
62/100
Blocked
56%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,210,046 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w08w19w210w311w412w516w517w618w119w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x256918f1…c4d0
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xdc9deb0a…4285
0x34b655…2a6f
6 touches
3 conflicts
0x4402c2ee…a884
0x34b655…2a6f
6 touches
3 conflicts
0x6aa624fd…a852
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity