← previous blocknext block →recent activity
Analyzing
Block #95,427,221
12 transactions · 12 stateful · 2026-08-12 19:22:16 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,427,221 · 12 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
1w02w13w24w35w07w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x3c5ea1e9…7e5a
0x34b655…2a6f
8 touches
6 conflicts
0xb754a75b…7cb9
0x34b655…2a6f
6 touches
3 conflicts
0x224d6800…4508
0x34b655…2a6f
6 touches
3 conflicts
0x7d915951…e4f9
0x34b655…2a6f
6 touches
3 conflicts
0x66e23978…c87c
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
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
6 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity