← previous blocknext block →recent activity
Analyzing
Block #89,748,734
12 transactions · 11 stateful · 2026-07-23 22:20:18 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,748,734 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f600d51…ffed
0x34b655…2a6f
4 touches
1 conflict
0xc6b604e6…5152
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x038b9243…553d
0x34b655…2a6f
2 touches
0 conflicts
0x1b6d4bf7…41e8
0x34b655…2a6f
2 touches
0 conflicts
0x23777feb…7f88
0x34b655…2a6f
2 touches
0 conflicts
0x24551912…0fa7
0x34b655…2a6f
2 touches
0 conflicts
0x2bf3a4c0…99c0
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x6f600d51e2…10ffed
Audit this contract →
← previous block·next block →recent activity