← previous blocknext block →recent activity
Analyzing
Block #95,000,244
26 transactions · 21 stateful · 2026-08-11 07:20:11 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.85
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,000,244 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w27w014w015w116w217w118w320w221w325w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c51d9aa…af39
0x34b655…2a6f
8 touches
6 conflicts
0x808e5184…881b
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x53f393fa…00b9
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
6 touches
3 conflicts
0x9cf9008a…d826
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x7c51d9aa1a…7faf39
Audit this contract →
← previous block·next block →recent activity