← previous blocknext block →recent activity
Analyzing
Block #96,267,469
21 transactions · 19 stateful · 2026-08-15 17:50:05 UTC
Parallelism
76/100
Blocked
26%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,267,469 · 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
1w02w15w06w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xec2ab287…49a3
0x34b655…2a6f
6 touches
3 conflicts
0x6b17f7a0…af41
0x34b655…2a6f
6 touches
3 conflicts
0x21f2dd42…3430
0x34b655…2a6f
4 touches
1 conflict
0xd5359d85…0bd8
0x34b655…2a6f
4 touches
1 conflict
0xa87df083…3166
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity