← previous blocknext block →recent activity
Analyzing
Block #89,575,117
19 transactions · 17 stateful · 2026-07-23 05:29:59 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,575,117 · 19 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
3w04w16w08w110w111w012w214w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe068f0d8…ac71
0x34b655…2a6f
6 touches
3 conflicts
0x81dbafca…d1ea
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x9e70dadd…810e
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x21e273cb…b384
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 0xe068f0d8f8…1dac71
Audit this contract →
← previous block·next block →recent activity