← previous blocknext block →recent activity
Analyzing
Block #89,844,486
22 transactions · 19 stateful · 2026-07-24 06:23:36 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,844,486 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w210w011w112w213w216w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x918c1e9d…964b
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x2bbc0cfb…c2c2
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x424934c8…f2f1
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 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity