← previous blocknext block →recent activity
Analyzing
Block #94,975,761
16 transactions · 15 stateful · 2026-08-11 05:17:03 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,975,761 · 16 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
1w02w13w04w05w16w28w010w111w012w114w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0xf7640726…19a2
0x2a68ba…90c5
4 touches
1 conflict
0x08d53462…97ef
0x2b46c0…1669
4 touches
1 conflict
0x5a409e7f…09b6
0x2b46c0…1669
4 touches
1 conflict
0x7a12283f…b18a
0x2b46c0…1669
4 touches
1 conflict
0x915c095e…c1e5
0x2b46c0…1669
4 touches
1 conflict
0xcfe06a18…b5b5
0x2b46c0…1669
4 touches
1 conflict
0xd8fd2add…50fc
0x2b46c0…1669
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 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity