← previous blocknext block →recent activity
Analyzing
Block #89,542,365
25 transactions · 23 stateful · 2026-07-23 01:51:09 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,542,365 · 25 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
1w02w13w07w08w19w010w111w212w314w215w116w317w023w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb06d06b…624d
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0xdb06d06b…6249
0x0a2fbf…29b1
8 touches
6 conflicts
0xdb06d06b…624a
0x0a2fbf…29b1
8 touches
6 conflicts
0xee3554d5…e6e8
0x0a2fbf…29b1
8 touches
6 conflicts
0xee3554d5…e6e9
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x1bff683e…7ecb
0x754704…b603
8 touches
6 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
6 conflicts on slot 0xdb06d06b0d…8c624d
Audit this contract →
← previous block·next block →recent activity