← previous blocknext block →recent activity
Analyzing
Block #89,860,165
19 transactions · 15 stateful · 2026-07-24 07:42:29 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,860,165 · 19 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
6w07w18w211w312w413w517w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
6 touches
3 conflicts
0xf0d45ffd…89cf
0x34b655…2a6f
6 touches
3 conflicts
0x2d030494…3283
0x34b655…2a6f
4 touches
1 conflict
0x379dc435…6616
0x34b655…2a6f
4 touches
1 conflict
0x47f1c421…ce9c
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity