← previous blocknext block →recent activity
Analyzing
Block #96,211,180
18 transactions · 17 stateful · 2026-08-15 13:06:58 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,211,180 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w17w28w39w410w512w316w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea1b8c07…b969
0x34b655…2a6f
10 touches
10 conflicts
0xafb8e71e…9285
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x9a3463f0…0b73
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa5a8ffca…8de2
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
10 conflicts on slot 0xea1b8c07ee…d0b969
Audit this contract →
← previous block·next block →recent activity