← previous blocknext block →recent activity
Analyzing
Block #89,747,414
16 transactions · 13 stateful · 2026-07-23 22:13:38 UTC
Parallelism
75/100
Blocked
46%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,747,414 · 16 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
1w02w14w06w07w18w19w210w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c6b7fa2…632f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x117d6c19…993c
0x40c49f…2af0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x45321d59…fc8a
0x34b655…2a6f
4 touches
1 conflict
0x5e800a72…0189
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
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 0x8c6b7fa26e…ea632f
Audit this contract →
← previous block·next block →recent activity