← previous blocknext block →recent activity
Analyzing
Block #95,573,116
16 transactions · 14 stateful · 2026-08-13 07:36:05 UTC
Parallelism
69/100
Blocked
29%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,573,116 · 16 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
1w02w13w27w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2840c278…bbc7
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xf607560e…828a
0x34b655…2a6f
4 touches
1 conflict
0x75023825…0cfc
0x34b655…2a6f
2 touches
0 conflicts
0x84eec99b…b0e6
0x34b655…2a6f
2 touches
0 conflicts
0x8cd0e64d…42bd
0x34b655…2a6f
2 touches
0 conflicts
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 0x2840c278a3…01bbc7
Audit this contract →
← previous block·next block →recent activity