← previous blocknext block →recent activity
Analyzing
Block #96,032,171
24 transactions · 22 stateful · 2026-08-14 22:06:33 UTC
Parallelism
75/100
Blocked
55%
Avg conflicts / tx
1.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,032,171 · 24 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
2w03w04w15w26w312w213w014w115w219w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5ea108a…dbf6
0x34b655…2a6f
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x4c188934…158e
0x34b655…2a6f
10 touches
10 conflicts
0x4b4060ee…995c
0xe52b14…7230
9 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xf5ea108a6a…e5dbf6
Audit this contract →
← previous block·next block →recent activity