← previous blocknext block →recent activity
Analyzing
Block #96,495,368
12 transactions · 10 stateful · 2026-08-16 12:56:19 UTC
Parallelism
58/100
Blocked
70%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,495,368 · 12 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
1w02w13w04w15w16w27w38w410w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf59d5c4…7b64
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab0
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 0xcf59d5c48d…e77b64
Audit this contract →
← previous block·next block →recent activity