← previous blocknext block →recent activity
Analyzing
Block #95,075,328
15 transactions · 14 stateful · 2026-08-11 13:38:41 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,075,328 · 15 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
3w04w15w06w17w28w09w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf36587f6…b0a2
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x981b7617…6093
0x34b655…2a6f
4 touches
1 conflict
0xb813a2aa…4d6b
0x34b655…2a6f
4 touches
1 conflict
0xbcab7dbe…2825
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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 0xf36587f6dc…62b0a2
Audit this contract →
← previous block·next block →recent activity