← previous blocknext block →recent activity
Analyzing
Block #94,841,154
18 transactions · 18 stateful · 2026-08-10 18:00:02 UTC
Parallelism
72/100
Blocked
28%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,841,154 · 18 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
1w02w13w04w15w26w09w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1482428…45f3
0x34b655…2a6f
10 touches
10 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x54d68470…4b32
0x34b655…2a6f
4 touches
1 conflict
0x60a536a6…ef7a
0x34b655…2a6f
4 touches
1 conflict
0x6636a104…d595
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 0xb148242857…a345f3
Audit this contract →
← previous block·next block →recent activity