← previous blocknext block →recent activity
Analyzing
Block #95,179,132
14 transactions · 12 stateful · 2026-08-11 22:20:51 UTC
Parallelism
57/100
Blocked
58%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,179,132 · 14 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
2w03w14w05w16w27w38w49w510w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2991489…c7ad
0x40c49f…2af0
12 touches
15 conflicts
0x2b54cadb…4425
0xd18b7e…414b
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x6518075e…2b17
0x2a68ba…90c5
12 touches
15 conflicts
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x991e2e20…94a6
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
15 conflicts on slot 0xf299148989…c1c7ad
Audit this contract →
← previous block·next block →recent activity