← previous blocknext block →recent activity
Analyzing
Block #95,745,284
16 transactions · 13 stateful · 2026-08-13 22:03:06 UTC
Parallelism
63/100
Blocked
62%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,745,284 · 16 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
2w03w14w25w36w47w08w19w214w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bd95eb4…e562
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x286ff32c…2782
0x34b655…2a6f
4 touches
1 conflict
0x312c6e56…3d7a
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x4efae872…6aa8
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 0x0bd95eb406…f6e562
Audit this contract →
← previous block·next block →recent activity