← previous blocknext block →recent activity
Analyzing
Block #89,404,605
32 transactions · 30 stateful · 2026-07-22 10:30:49 UTC
Parallelism
84/100
Blocked
57%
Avg conflicts / tx
1.03
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,404,605 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w07w18w29w310w411w012w113w215w016w123w224w130w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x11b69a7e…334e
0x01bff4…1071
8 touches
6 conflicts
0x628ca14e…e0f9
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x6fe7d366…78ff
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: 0x48cba278…e2b48b
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity