← previous blocknext block →recent activity
Analyzing
Block #95,270,343
20 transactions · 18 stateful · 2026-08-12 06:08:23 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,270,343 · 20 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
2w03w14w05w16w27w38w410w011w112w213w217w318w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0x6518075e…2b17
0x2a68ba…90c5
8 touches
6 conflicts
0x6ec14d89…6538
0x40c49f…2af0
7 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0xf0d45ffd…89cf
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xbec23443…9293
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
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
10 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity