← previous blocknext block →recent activity
Analyzing
Block #95,586,867
18 transactions · 14 stateful · 2026-08-13 08:45:15 UTC
Parallelism
83/100
Blocked
21%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,586,867 · 18 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
2w04w18w011w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x468d132a…d7b8
0x34b655…2a6f
6 touches
3 conflicts
0x9e24a1a6…16a1
0x34b655…2a6f
4 touches
1 conflict
0x9f121162…fdfe
0x34b655…2a6f
4 touches
1 conflict
0xb8fec4f2…0e62
0x34b655…2a6f
4 touches
1 conflict
0x5e2ea201…12de
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x7938c6fd…1cd1
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 0x468d132ac7…d0d7b8
Audit this contract →
← previous block·next block →recent activity