← previous blocknext block →recent activity
Analyzing
Block #96,596,347
7 transactions · 7 stateful · 2026-08-16 21:24:30 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,596,347 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd192f4ed…d7ec
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0x00c43e68…2a3c
0x34b655…2a6f
2 touches
0 conflicts
0x033cf007…136d
0x34b655…2a6f
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x4c24db4d…1fed
0x34b655…2a6f
2 touches
0 conflicts
0x5b30a6e6…b249
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xd192f4edae…03d7ec
Audit this contract →
← previous block·next block →recent activity