← previous blocknext block →recent activity
Analyzing
Block #96,483,036
14 transactions · 12 stateful · 2026-08-16 11:54:17 UTC
Parallelism
71/100
Blocked
58%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,483,036 · 14 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
1w02w04w15w16w17w28w211w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0x12f97307…97c3
0x34b655…2a6f
6 touches
3 conflicts
0x46db48f8…9bff
0x34b655…2a6f
6 touches
3 conflicts
0x68ca40a2…bc7c
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0xfa3d71b4…937f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity