← previous blocknext block →recent activity
Analyzing
Block #94,954,051
10 transactions · 9 stateful · 2026-08-11 03:27:52 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,954,051 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2e35622…f491
0x34b655…2a6f
4 touches
1 conflict
0x2a49400d…643d
0x34b655…2a6f
4 touches
1 conflict
0x4a6b3039…6a98
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x03a6363b…ad2b
0x34b655…2a6f
2 touches
0 conflicts
0x20db9d81…71df
0x34b655…2a6f
2 touches
0 conflicts
0x238a3e64…a4fa
0x34b655…2a6f
2 touches
0 conflicts
0x962713d6…7374
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xd2e3562276…b0f491
Audit this contract →
← previous block·next block →recent activity