← previous blocknext block →recent activity
Analyzing
Block #95,278,271
6 transactions · 5 stateful · 2026-08-12 06:48:23 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,278,271 · 6 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x01b746a4…6c41
0x34b655…2a6f
2 touches
0 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
2 touches
0 conflicts
0x070f03d7…b8a3
0x34b655…2a6f
2 touches
0 conflicts
0x1526b11f…8b21
0x34b655…2a6f
2 touches
0 conflicts
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x1669d3af…b37b
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
1 conflict on slot 0x91b0f8edc5…b76bd6
Audit this contract →
← previous block·next block →recent activity