← previous blocknext block →recent activity
Analyzing
Block #96,836,123
14 transactions · 14 stateful · 2026-08-17 17:30:29 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,836,123 · 14 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
1w03w16w07w18w212w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8eef368f…aa21
0x34b655…2a6f
8 touches
6 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0198a961…04dc
0x34b655…2a6f
4 touches
1 conflict
0x092b7171…c16d
0x34b655…2a6f
4 touches
1 conflict
0x378e1e8f…803c
0x34b655…2a6f
4 touches
1 conflict
0xb409e204…89ac
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
6 conflicts on slot 0x8eef368f1b…01aa21
Audit this contract →
← previous block·next block →recent activity