← previous blocknext block →recent activity
Analyzing
Block #96,033,304
18 transactions · 18 stateful · 2026-08-14 22:12:16 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,033,304 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w39w410w515w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fdc2ba7…0396
0x34b655…2a6f
10 touches
10 conflicts
0xd29144b1…30b5
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0f6aef87…8137
0x34b655…2a6f
8 touches
6 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
8 touches
6 conflicts
0x43bb28d7…7bd7
0x34b655…2a6f
8 touches
6 conflicts
0xfc371f5e…0955
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x4fdc2ba741…3b0396
Audit this contract →
← previous block·next block →recent activity