← previous blocknext block →recent activity
Analyzing
Block #89,689,047
13 transactions · 12 stateful · 2026-07-23 17:19:03 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,689,047 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w07w110w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x742436a7…c4d4
0x34b655…2a6f
6 touches
3 conflicts
0xa42c4f4c…038c
0x0a2fbf…29b1
4 touches
1 conflict
0xc5515c28…f661
0x0a2fbf…29b1
4 touches
1 conflict
0xc5515c28…f662
0x0a2fbf…29b1
4 touches
1 conflict
0xc5515c28…f665
0x0a2fbf…29b1
4 touches
1 conflict
0x5138188e…796b
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity