← previous blocknext block →recent activity
Analyzing
Block #96,219,763
18 transactions · 17 stateful · 2026-08-15 13:50:08 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,219,763 · 18 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
1w02w14w05w16w07w112w213w314w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07010ea7…c45a
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe6997d36…4f33
0x34b655…2a6f
6 touches
3 conflicts
0x9ffe92a7…4811
0x34b655…2a6f
5 touches
3 conflicts
0x6d1b72ee…6b78
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 0x07010ea7a3…72c45a
Audit this contract →
← previous block·next block →recent activity