← previous blocknext block →recent activity
Analyzing
Block #89,741,802
11 transactions · 11 stateful · 2026-07-23 21:45:17 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,741,802 · 11 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
1w03w15w26w310w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f1b11a2…45b7
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0xc13e1d5c…62c6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
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 0xf2f4727df6…a5cdb7
Audit this contract →
← previous block·next block →recent activity