← previous blocknext block →recent activity
Analyzing
Block #96,288,529
17 transactions · 15 stateful · 2026-08-15 19:36:00 UTC
Parallelism
53/100
Blocked
53%
Avg conflicts / tx
1.76
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,288,529 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w37w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4b80417b…75c3
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x948e8d20…a8df
0x34b655…2a6f
4 touches
1 conflict
0x9d6d235c…3d64
0x34b655…2a6f
4 touches
1 conflict
0xa9f8096f…f132
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
28 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity