← previous blocknext block →recent activity
Analyzing
Block #89,580,969
12 transactions · 9 stateful · 2026-07-23 06:08:59 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,580,969 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d02a2c5…9802
0x34b655…2a6f
4 touches
1 conflict
0xf0511a49…bc4d
0x0a2fbf…29b1
4 touches
1 conflict
0xf0511a49…bc50
0x0a2fbf…29b1
4 touches
1 conflict
0x55b4e430…44cb
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0xf0511a49…bc4c
0x0a2fbf…29b1
4 touches
1 conflict
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x0fc41e7b…6831
0x98dc6e…8633
2 touches
0 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: Perpl
1 conflict on slot 0x7d02a2c5be…4c9802
Audit this contract →
← previous block·next block →recent activity