← previous blocknext block →recent activity
Analyzing
Block #89,542,814
12 transactions · 11 stateful · 2026-07-23 01:54:09 UTC
Parallelism
58/100
Blocked
45%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,542,814 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w27w18w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb476ee35…c627
0xa6afd3…d132
4 touches
1 conflict
0x41377979…0a18
0x34b655…2a6f
4 touches
1 conflict
0xfda9e59e…c662
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x405da62e…192a
0xa6afd3…d132
4 touches
1 conflict
0x4102cb2a…3b17
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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity