← previous blocknext block →recent activity
Analyzing
Block #96,828,000
20 transactions · 19 stateful · 2026-08-17 16:49:37 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,828,000 · 20 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
1w02w03w14w25w16w37w48w510w011w114w615w218w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f92891d…fcde
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
8 touches
6 conflicts
0x833f3561…bfd0
0x34b655…2a6f
6 touches
3 conflicts
0x3c78ca04…432c
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x52b477bc…7ccf
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 0x3f92891d2d…f3fcde
Audit this contract →
← previous block·next block →recent activity