← previous blocknext block →recent activity
Analyzing
Block #95,394,714
17 transactions · 16 stateful · 2026-08-12 16:37:56 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,394,714 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w111w415w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x224d6800…4508
0x34b655…2a6f
6 touches
3 conflicts
0xbf9d3917…2850
0x34b655…2a6f
6 touches
3 conflicts
0x7d915951…e4f9
0x34b655…2a6f
6 touches
3 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0x6b47245e…a342
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0x86977b3d…a9c4
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
3 conflicts on slot 0x224d68002e…0e4508
Audit this contract →
← previous block·next block →recent activity