← previous blocknext block →recent activity
Analyzing
Block #96,358,134
31 transactions · 28 stateful · 2026-08-16 01:26:05 UTC
Parallelism
74/100
Blocked
71%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,358,134 · 31 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w17w08w19w010w111w112w013w214w315w417w118w519w623w324w225w529w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85e59464…9104
0x34b655…2a6f
8 touches
6 conflicts
0x424934c8…f2f1
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x9a3463f0…0b73
0x34b655…2a6f
8 touches
6 conflicts
0xf219f7cf…7379
0xa6afd3…d132
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
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 0x85e594647f…5d9104
Audit this contract →
← previous block·next block →recent activity