← previous blocknext block →recent activity
Analyzing
Block #95,150,738
15 transactions · 14 stateful · 2026-08-11 19:58:02 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,150,738 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w18w19w210w312w214w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c0d2f30…1afb
0x34b655…2a6f
8 touches
6 conflicts
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x6dfe90e8…a88a
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x33b5035a…d1c6
0x34b655…2a6f
4 touches
1 conflict
0x4702a1f4…1fea
0x34b655…2a6f
4 touches
1 conflict
0x4c619b7d…f4fa
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 0x3c0d2f30c0…ee1afb
Audit this contract →
← previous block·next block →recent activity