← previous blocknext block →recent activity
Analyzing
Block #89,580,614
16 transactions · 12 stateful · 2026-07-23 06:06:37 UTC
Parallelism
81/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,580,614 · 16 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
3w06w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa93224c6…ced5
0x34b655…2a6f
4 touches
1 conflict
0x580a0974…3d53
0x34b655…2a6f
4 touches
1 conflict
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0xe751731d…9aa5
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x521553ff…d548
0x34b655…2a6f
4 touches
1 conflict
0xa93224c6…ced4
0x34b655…2a6f
4 touches
1 conflict
0x9c7d2e4b…499b
0x34b655…2a6f
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 0xa93224c6b8…05ced5
Audit this contract →
← previous block·next block →recent activity