← previous blocknext block →recent activity
Analyzing
Block #96,264,718
5 transactions · 5 stateful · 2026-08-15 17:36:15 UTC
Parallelism
40/100
Blocked
40%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,264,718 · 5 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec2ab287…49a3
0x34b655…2a6f
4 touches
1 conflict
0x4b76146e…0dcb
0x34b655…2a6f
4 touches
1 conflict
0x6b17f7a0…af41
0x34b655…2a6f
4 touches
1 conflict
0xadf9bdd6…103e
0x34b655…2a6f
4 touches
1 conflict
0x0eb3ab36…88ba
0x34b655…2a6f
2 touches
0 conflicts
0x28023fa2…8bf8
0x34b655…2a6f
2 touches
0 conflicts
0x2b2cf495…1c6f
0x34b655…2a6f
2 touches
0 conflicts
0x2b2cf495…1c70
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 0xec2ab28745…7a49a3
Audit this contract →
← previous block·next block →recent activity