← previous blocknext block →recent activity
Analyzing
Block #95,193,042
21 transactions · 20 stateful · 2026-08-11 23:30:49 UTC
Parallelism
62/100
Blocked
50%
Avg conflicts / tx
1.62
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,193,042 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w28w09w110w211w312w413w514w615w716w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde6176aa…ea31
0x40c49f…2af0
16 touches
28 conflicts
0xa1087a5c…66c4
0x754704…b603
16 touches
28 conflicts
0x2b54cadb…4425
0xd18b7e…414b
16 touches
28 conflicts
0x6518075e…2b17
0x2a68ba…90c5
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9689c02b…3984
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: 0x40c49f17…d22af0
28 conflicts on slot 0xde6176aa4d…a1ea31
Audit this contract →
← previous block·next block →recent activity