← previous blocknext block →recent activity
Analyzing
Block #95,076,035
11 transactions · 11 stateful · 2026-08-11 13:42:15 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,076,035 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w26w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0d45ffd…89cf
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x115c1228…a58f
0x34b655…2a6f
2 touches
0 conflicts
0x2c0fe9aa…dad9
0x34b655…2a6f
2 touches
0 conflicts
0x30621d87…1951
0x34b655…2a6f
2 touches
0 conflicts
0x45911da6…5523
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xf0d45ffdb0…4089cf
Audit this contract →
← previous block·next block →recent activity