← previous blocknext block →recent activity
Analyzing
Block #95,173,571
20 transactions · 18 stateful · 2026-08-11 21:52:52 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,173,571 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w29w010w111w212w313w415w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x424934c8…f2f1
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
8 touches
6 conflicts
0x6518075e…2b17
0x2a68ba…90c5
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x6eeddfea…c168
0x40c49f…2af0
5 touches
3 conflicts
0xccbd5679…119d
0x40c49f…2af0
5 touches
3 conflicts
0xe9ff2c5d…0474
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 0x424934c865…4af2f1
Audit this contract →
← previous block·next block →recent activity