← previous blocknext block →recent activity
Analyzing
Block #95,710,021
11 transactions · 11 stateful · 2026-08-13 19:05:32 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,710,021 · 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
1w04w07w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x957c875f…b3f9
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf1345bef…5530
0x34b655…2a6f
4 touches
1 conflict
0x2a2fcb7f…9ae6
0x34b655…2a6f
2 touches
0 conflicts
0x3d49013e…1338
0x34b655…2a6f
2 touches
0 conflicts
0x427d1120…4eb1
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 0x957c875f2a…99b3f9
Audit this contract →
← previous block·next block →recent activity