← previous blocknext block →recent activity
Analyzing
Block #95,413,220
13 transactions · 12 stateful · 2026-08-12 18:11:36 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,413,220 · 13 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
1w02w13w05w16w27w312w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a42683d…6f4f
0x34b655…2a6f
6 touches
3 conflicts
0x6a82e505…693a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad07
0x34b655…2a6f
6 touches
3 conflicts
0x388633a0…86cd
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xfd2a6546…6168
0x34b655…2a6f
5 touches
3 conflicts
0x2fd61111…5bbc
0x34b655…2a6f
4 touches
1 conflict
0x3eae31ad…600e
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
3 conflicts on slot 0x0a42683dda…f36f4f
Audit this contract →
← previous block·next block →recent activity