← previous blocknext block →recent activity
Analyzing
Block #89,277,173
15 transactions · 13 stateful · 2026-07-21 20:19:03 UTC
Parallelism
73/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,277,173 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x5bbf50c8…cb27
0x34b655…2a6f
4 touches
1 conflict
0x5cf287d1…d392
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x2697123c…8526
0x34b655…2a6f
4 touches
1 conflict
0x7525206c…fbd5
0x34b655…2a6f
4 touches
1 conflict
0xc9dce17a…a1a1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x58620f2942…18db5a
Audit this contract →
← previous block·next block →recent activity