← previous blocknext block →recent activity
Analyzing
Block #95,758,830
15 transactions · 13 stateful · 2026-08-13 23:11:14 UTC
Parallelism
73/100
Blocked
46%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,758,830 · 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
2w05w16w27w08w110w311w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x0778475b…bd75
0x2a68ba…90c5
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xeead26fc…98cc
0x065c9d…c394
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x4c1ccbe6…0767
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity