← previous blocknext block →recent activity
Analyzing
Block #96,591,818
24 transactions · 22 stateful · 2026-08-16 21:01:43 UTC
Parallelism
79/100
Blocked
45%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,591,818 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w08w09w110w212w013w316w117w018w220w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x90c374…be45
8 touches
6 conflicts
0x745952b2…d90c
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…000a
0x90c374…be45
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x0a6c31fc…f4c3
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0x424934c8…f2f1
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
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: 0x90c3747c…0ebe45
6 conflicts on slot 0x0000000000…00000b
Audit this contract →
← previous block·next block →recent activity