← previous blocknext block →recent activity
Analyzing
Block #89,525,981
13 transactions · 12 stateful · 2026-07-23 00:01:49 UTC
Parallelism
62/100
Blocked
50%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,525,981 · 13 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
1w02w14w05w16w17w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85bfd0af…ce96
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0x941bd594…21fd
0x34b655…2a6f
6 touches
3 conflicts
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x076d2329…495d
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 0x85bfd0afba…f5ce96
Audit this contract →
← previous block·next block →recent activity