← previous blocknext block →recent activity
Analyzing
Block #89,599,005
21 transactions · 20 stateful · 2026-07-23 08:09:27 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,599,005 · 21 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
2w03w15w06w17w28w39w110w211w312w413w214w519w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65104f89…bbce
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x403a02ac…b163
0x34b655…2a6f
6 touches
3 conflicts
0xdb6dd5ad…0a91
0x34b655…2a6f
6 touches
3 conflicts
0xd972ea45…48b5
0x34b655…2a6f
6 touches
3 conflicts
0x638d2cf4…1db2
0x34b655…2a6f
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 0x65104f8913…a8bbce
Audit this contract →
← previous block·next block →recent activity