← previous blocknext block →recent activity
Analyzing
Block #89,570,678
14 transactions · 13 stateful · 2026-07-23 05:00:22 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.71
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,570,678 · 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
4w05w16w17w28w29w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ca268be…8865
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1bff683e…7ecb
0x754704…b603
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xed7b8253…03ce
0x34b655…2a6f
6 touches
3 conflicts
0x9211e33e…0b61
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
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
3 conflicts on slot 0x3ca268be3f…e98865
Audit this contract →
← previous block·next block →recent activity