← previous blocknext block →recent activity
Analyzing
Block #95,351,065
13 transactions · 10 stateful · 2026-08-12 12:56:50 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,351,065 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w07w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x320701d5…f9f3
0x34b655…2a6f
4 touches
1 conflict
0xace3c59c…ac2f
0x34b655…2a6f
4 touches
1 conflict
0xb8f17c81…df37
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0xa46bb02d…6b2d
0x928dc8…8207
4 touches
1 conflict
0xc4e19ae4…0788
0xe7cd86…c82d
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
1 conflict on slot 0x320701d57e…e5f9f3
Audit this contract →
← previous block·next block →recent activity