← previous blocknext block →recent activity
Analyzing
Block #89,549,194
29 transactions · 25 stateful · 2026-07-23 02:36:48 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,549,194 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w09w115w016w117w318w219w320w422w523w024w126w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x6e19c9a0…7d86
0x34b655…2a6f
8 touches
6 conflicts
0xb900efa2…8624
0x34b655…2a6f
8 touches
6 conflicts
0xfd02758d…8774
0xd32edf…ff58
7 touches
6 conflicts
0x69411fb3…e36d
0x34b655…2a6f
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x3fa1fac4…826c
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity