← previous blocknext block →recent activity
Analyzing
Block #89,414,798
14 transactions · 13 stateful · 2026-07-22 11:38:57 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,414,798 · 14 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
1w05w16w07w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69e1bf5f…349a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb4d9cd77…0c88
0x34b655…2a6f
4 touches
1 conflict
0xb25fa8e2…c9ef
0x34b655…2a6f
4 touches
1 conflict
0x966352c5…060c
0x34b655…2a6f
4 touches
1 conflict
0x00f7bf52…503b
0x34b655…2a6f
4 touches
1 conflict
0x0f1cb25b…2764
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
1 conflict on slot 0x69e1bf5ff2…98349a
Audit this contract →
← previous block·next block →recent activity