← previous blocknext block →recent activity
Analyzing
Block #96,293,539
10 transactions · 9 stateful · 2026-08-15 20:01:12 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,293,539 · 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
2w03w04w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7277122…8339
0x34b655…2a6f
6 touches
3 conflicts
0xc3071bdb…d4bf
0x34b655…2a6f
6 touches
3 conflicts
0xe8927855…7e59
0x34b655…2a6f
6 touches
3 conflicts
0x75586248…f0b4
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0xc7277122f3…a98339
Audit this contract →
← previous block·next block →recent activity