← previous blocknext block →recent activity
Analyzing
Block #94,953,822
16 transactions · 14 stateful · 2026-08-11 03:26:43 UTC
Parallelism
63/100
Blocked
36%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,953,822 · 16 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
1w02w03w14w06w27w38w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21cb35dd…1f66
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
8 touches
6 conflicts
0x2aab0897…78f7
0x34b655…2a6f
6 touches
3 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
4 touches
1 conflict
0x8f791153…4f53
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
10 conflicts on slot 0x21cb35dd46…db1f66
Audit this contract →
← previous block·next block →recent activity