← previous blocknext block →recent activity
Analyzing
Block #94,696,936
11 transactions · 11 stateful · 2026-08-10 05:53:07 UTC
Parallelism
55/100
Blocked
45%
Avg conflicts / tx
0.91
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,696,936 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f600d51…ffed
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x2bf3a4c0…99c0
0x34b655…2a6f
4 touches
1 conflict
0x455cc08d…26b6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4bc1abab…5874
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
6 conflicts on slot 0x6f600d51e2…10ffed
Audit this contract →
← previous block·next block →recent activity