← previous blocknext block →recent activity
Analyzing
Block #96,365,662
17 transactions · 15 stateful · 2026-08-16 02:03:57 UTC
Parallelism
59/100
Blocked
47%
Avg conflicts / tx
1.47
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,365,662 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w311w412w513w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67459137…de7e
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x000bde1a…e123
0x34b655…2a6f
10 touches
10 conflicts
0x9a3463f0…0b73
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x52650965…4904
0x34b655…2a6f
7 touches
6 conflicts
0x6c28863e…840e
0x34b655…2a6f
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
21 conflicts on slot 0x67459137b2…7dde7e
Audit this contract →
← previous block·next block →recent activity