← previous blocknext block →recent activity
Analyzing
Block #89,853,820
25 transactions · 22 stateful · 2026-07-24 07:10:34 UTC
Parallelism
88/100
Blocked
45%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,853,820 · 25 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
1w02w13w14w05w18w010w111w213w214w216w017w118w223w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01385df7…f301
0x0a2fbf…29b1
6 touches
3 conflicts
0x01385df7…f302
0x0a2fbf…29b1
6 touches
3 conflicts
0x01385df7…f305
0x0a2fbf…29b1
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0005
0x370e2e…63b4
6 touches
3 conflicts
0xf4fbf3e4…2610
0x370e2e…63b4
6 touches
3 conflicts
0x1bff683e…7ecb
0x754704…b603
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
6 touches
3 conflicts
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: 0x0a2fbf2d…f729b1
3 conflicts on slot 0x01385df7bf…2af301
Audit this contract →
← previous block·next block →recent activity