← previous blocknext block →recent activity
Analyzing
Block #89,870,133
13 transactions · 13 stateful · 2026-07-24 08:32:38 UTC
Parallelism
54/100
Blocked
46%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,870,133 · 13 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
2w04w15w26w37w48w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2130a548…c1de
0x34b655…2a6f
6 touches
3 conflicts
0xbd9491f7…dd92
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xf8367206…a090
0x34b655…2a6f
4 touches
1 conflict
0x5ebff854…1952
0x34b655…2a6f
4 touches
1 conflict
0x74e46435…fdcd
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x2130a548b9…31c1de
Audit this contract →
← previous block·next block →recent activity