← previous blocknext block →recent activity
Analyzing
Block #95,023,924
19 transactions · 19 stateful · 2026-08-11 09:19:20 UTC
Parallelism
89/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,023,924 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w07w110w011w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9f0b0dc…4827
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x920fdd9d…09de
0x34b655…2a6f
2 touches
0 conflicts
0x9aaca373…d7c0
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 0xb9f0b0dc52…ec4827
Audit this contract →
← previous block·next block →recent activity