← previous blocknext block →recent activity
Analyzing
Block #94,798,444
21 transactions · 20 stateful · 2026-08-10 14:25:10 UTC
Parallelism
67/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,798,444 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w013w117w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2840c278…bbc7
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd145574b…436f
0x34b655…2a6f
4 touches
1 conflict
0xddf08cbf…2ba3
0x34b655…2a6f
4 touches
1 conflict
0xf8f1e808…a4fd
0x34b655…2a6f
4 touches
1 conflict
0xfbe6a366…8ca1
0x34b655…2a6f
4 touches
1 conflict
0x6f1bd077…2005
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x2840c278a3…01bbc7
Audit this contract →
← previous block·next block →recent activity