← previous blocknext block →recent activity
Analyzing
Block #89,675,859
18 transactions · 16 stateful · 2026-07-23 16:12:24 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,675,859 · 18 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
2w03w05w18w09w111w012w114w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x861e5aef…d32c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3b47e45c…7b87
0x34b655…2a6f
4 touches
1 conflict
0x40a6de3a…0973
0x34b655…2a6f
4 touches
1 conflict
0x4954a433…820d
0x34b655…2a6f
4 touches
1 conflict
0x562ef8b5…2a7d
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x08c1b53c…7316
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
3 conflicts on slot 0x861e5aeffa…5cd32c
Audit this contract →
← previous block·next block →recent activity