← previous blocknext block →recent activity
Analyzing
Block #96,276,603
44 transactions · 44 stateful · 2026-08-15 18:36:02 UTC
Parallelism
89/100
Blocked
9%
Avg conflicts / tx
0.16
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,276,603 · 44 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
1w02w13w24w342w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x18e86f02…fa98
0x34b655…2a6f
6 touches
3 conflicts
0x45c77748…3d83
0x34b655…2a6f
6 touches
3 conflicts
0x2d62181c…a99f
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity