← previous blocknext block →recent activity
Analyzing
Block #94,847,328
18 transactions · 16 stateful · 2026-08-10 18:31:06 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,847,328 · 18 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
2w03w14w17w28w39w410w313w414w515w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xcef70a96…db44
0x34b655…2a6f
6 touches
3 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
6 touches
3 conflicts
0x021df0f6…5d6f
0x34b655…2a6f
6 touches
3 conflicts
0xa07e7b13…7513
0x34b655…2a6f
4 touches
1 conflict
0xb480d016…0fce
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity