← previous blocknext block →recent activity
Analyzing
Block #95,976,856
10 transactions · 8 stateful · 2026-08-14 17:28:11 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,976,856 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0d3a786…91d9
0x34b655…2a6f
8 touches
6 conflicts
0x640fd1c6…d624
0x34b655…2a6f
6 touches
3 conflicts
0x78b52df8…344b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x59a7a3f4…62fd
0x34b655…2a6f
4 touches
1 conflict
0x236533a6…52ac
0x34b655…2a6f
2 touches
0 conflicts
0x2d6af7d3…5e30
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
6 conflicts on slot 0xa0d3a786de…b991d9
Audit this contract →
← previous block·next block →recent activity