← previous blocknext block →recent activity
Analyzing
Block #96,294,767
16 transactions · 15 stateful · 2026-08-15 20:07:23 UTC
Parallelism
50/100
Blocked
53%
Avg conflicts / tx
2.25
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,294,767 · 16 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
1w02w13w24w05w38w49w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x28be48f5…d50b
0x34b655…2a6f
10 touches
10 conflicts
0x4c4b7a66…c877
0x34b655…2a6f
8 touches
6 conflicts
0xdbb2fff3…b121
0x34b655…2a6f
6 touches
3 conflicts
0xe283e878…7262
0x34b655…2a6f
6 touches
3 conflicts
0xe999cbf5…d18a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity