← previous blocknext block →recent activity
Analyzing
Block #96,545,975
21 transactions · 20 stateful · 2026-08-16 17:11:08 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,545,975 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w08w09w110w211w314w015w317w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
4 touches
1 conflict
0x8cf3d245…1d0d
0x2b46c0…1669
4 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
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 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity