← previous blocknext block →recent activity
Analyzing
Block #94,850,779
16 transactions · 15 stateful · 2026-08-10 18:48:28 UTC
Parallelism
50/100
Blocked
53%
Avg conflicts / tx
1.94
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,850,779 · 16 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
2w03w14w25w37w08w410w511w612w714w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
12 touches
15 conflicts
0x217dce8d…7e14
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x117d1e0c…e669
0x34b655…2a6f
4 touches
1 conflict
0x1e737223…2278
0x34b655…2a6f
4 touches
1 conflict
0x3cf50d44…961b
0x34b655…2a6f
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