← previous blocknext block →recent activity
Analyzing
Block #96,640,479
21 transactions · 19 stateful · 2026-08-17 01:06:27 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,640,479 · 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
1w02w13w04w15w06w17w29w010w111w212w313w216w317w418w520w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74b66dfb…1ed4
0x34b655…2a6f
10 touches
10 conflicts
0xea1b8c07…b969
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x103de0…bb55
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0x74b66dfba8…4c1ed4
Audit this contract →
← previous block·next block →recent activity