← previous blocknext block →recent activity
Analyzing
Block #96,709,002
24 transactions · 21 stateful · 2026-08-17 06:51:05 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.25
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,709,002 · 24 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
1w02w14w05w16w27w38w09w116w417w518w620w723w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x8cd684d0…c3cb
0x34b655…2a6f
8 touches
6 conflicts
0x5efd583e…c41a
0x34b655…2a6f
6 touches
3 conflicts
0x746bcce3…d0ce
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0xdb95e18e…c738
0x1b6862…e19c
4 touches
1 conflict
0x29a945df…bcd8
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity