← previous blocknext block →recent activity
Analyzing
Block #95,592,190
21 transactions · 17 stateful · 2026-08-13 09:12:01 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,592,190 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w17w28w29w313w414w517w119w020w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85167706…718e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xafb8e71e…9285
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xbcdd58ff…0711
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
4 touches
1 conflict
0x9210e826…1414
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 0x85167706bf…d5718e
Audit this contract →
← previous block·next block →recent activity