← previous blocknext block →recent activity
Analyzing
Block #89,860,186
10 transactions · 9 stateful · 2026-07-24 07:42:35 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,860,186 · 10 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
1w02w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48b13e5e…3c2a
0x34b655…2a6f
4 touches
1 conflict
0xa46242d8…c0a7
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x4360b49f…140d
0x34b655…2a6f
4 touches
1 conflict
0xdfe03173…66fd
0x34b655…2a6f
3 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x53e50026…6d8c
0x2b46c0…1669
2 touches
0 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
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 0x48b13e5e9b…6a3c2a
Audit this contract →
← previous block·next block →recent activity