← previous blocknext block →recent activity
Analyzing
Block #96,604,244
25 transactions · 20 stateful · 2026-08-16 22:04:13 UTC
Parallelism
72/100
Blocked
55%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,604,244 · 25 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
5w06w17w28w09w112w213w314w016w418w519w622w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
8 touches
6 conflicts
0x7a27fdde…8b23
0x34b655…2a6f
8 touches
6 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
8 touches
6 conflicts
0xabf57eb6…416d
0x34b655…2a6f
8 touches
6 conflicts
0x4340313d…6e83
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity