← previous blocknext block →recent activity
Analyzing
Block #89,758,790
14 transactions · 14 stateful · 2026-07-23 23:11:04 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,758,790 · 14 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
1w02w17w08w112w013w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb5d53a1…ad5f
0x34b655…2a6f
4 touches
1 conflict
0x08cc321f…91e1
0x34b655…2a6f
4 touches
1 conflict
0x0a07885c…0af8
0x34b655…2a6f
4 touches
1 conflict
0x2ac796c1…5bbc
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xeb5d53a114…6fad5f
Audit this contract →
← previous block·next block →recent activity