← previous blocknext block →recent activity
Analyzing
Block #96,032,202
21 transactions · 21 stateful · 2026-08-14 22:06:42 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,032,202 · 21 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
1w03w04w15w26w29w010w311w414w115w016w017w118w120w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x19c6728a…d6b4
0x065c9d…c394
4 touches
1 conflict
0xc4322d1d…9149
0x065c9d…c394
4 touches
1 conflict
0x2981b6be…7be0
0x34b655…2a6f
4 touches
1 conflict
0x32dfa6a9…12f6
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
10 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity