← previous blocknext block →recent activity
Analyzing
Block #89,744,745
19 transactions · 16 stateful · 2026-07-23 22:00:10 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,744,745 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w38w09w410w111w213w518w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x392a02b5…0019
0x81a224…7777
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4c770fe0…b972
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x714a26…182d
6 touches
3 conflicts
0x00000000…0003
0x714a26…182d
6 touches
3 conflicts
0xddc22bc2…7f7a
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: Perpl
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity