← previous blocknext block →recent activity
Analyzing
Block #96,016,614
15 transactions · 14 stateful · 2026-08-14 20:48:17 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,016,614 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w18w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd4a5ef1…e4c4
0x34b655…2a6f
8 touches
6 conflicts
0x37d710c8…45c1
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa8c5904c…e1a7
0x34b655…2a6f
4 touches
1 conflict
0xb9a63764…f004
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
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 0xfd4a5ef199…94e4c4
Audit this contract →
← previous block·next block →recent activity