← previous blocknext block →recent activity
Analyzing
Block #96,555,085
14 transactions · 13 stateful · 2026-08-16 17:56:57 UTC
Parallelism
57/100
Blocked
46%
Avg conflicts / tx
1.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,555,085 · 14 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
1w02w03w14w26w38w09w112w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
12 touches
15 conflicts
0x92e28bd4…72cc
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x4d66de6b…202b
0x34b655…2a6f
6 touches
3 conflicts
0x76c4467d…ce28
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x801e9566…9d4c
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
15 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity