← previous blocknext block →recent activity
Analyzing
Block #96,535,631
21 transactions · 14 stateful · 2026-08-16 16:19:06 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,535,631 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w08w09w111w112w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5997449…c2b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9e23744a…79b4
0x34b655…2a6f
4 touches
1 conflict
0x957c875f…b3f9
0x34b655…2a6f
4 touches
1 conflict
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x35b89cd8…5092
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 0xc599744981…f7c2b8
Audit this contract →
← previous block·next block →recent activity