← previous blocknext block →recent activity
Analyzing
Block #89,753,724
17 transactions · 15 stateful · 2026-07-23 22:45:31 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,753,724 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w010w011w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc204ea3…f1a3
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x59a54ff4…d21b
0x34b655…2a6f
6 touches
3 conflicts
0x91571b80…895b
0x0a2fbf…29b1
4 touches
1 conflict
0x91571b80…895c
0x0a2fbf…29b1
4 touches
1 conflict
0x91571b80…895f
0x0a2fbf…29b1
4 touches
1 conflict
0x91571b80…8961
0x0a2fbf…29b1
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 0xdc204ea323…a5f1a3
Audit this contract →
← previous block·next block →recent activity