← previous blocknext block →recent activity
Analyzing
Block #89,572,240
14 transactions · 13 stateful · 2026-07-23 05:10:48 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
1.14
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,572,240 · 14 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
2w04w05w17w18w29w311w012w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0xe068f0d8…ac71
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9e70dadd…810d
0x34b655…2a6f
6 touches
3 conflicts
0x9e70dadd…810e
0x34b655…2a6f
6 touches
3 conflicts
0xad364aa3…be78
0x34b655…2a6f
4 touches
1 conflict
0xba9f88e8…9c33
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
6 conflicts on slot 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity