← previous blocknext block →recent activity
Analyzing
Block #95,276,217
14 transactions · 13 stateful · 2026-08-12 06:38:03 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,276,217 · 14 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
1w02w13w24w05w38w410w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fbb30c7…4e58
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x7d81ec7b…64c3
0x34b655…2a6f
4 touches
1 conflict
0xa8b713a7…40ef
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 0x0fbb30c7d0…d74e58
Audit this contract →
← previous block·next block →recent activity