← previous blocknext block →recent activity
Analyzing
Block #89,580,806
16 transactions · 14 stateful · 2026-07-23 06:07:54 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,580,806 · 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
2w03w17w08w19w010w211w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6e41de2…7f6d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0413d1ed…ad55
0x34b655…2a6f
4 touches
1 conflict
0x04994ed2…9032
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x932a9590…0b19
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 0xb6e41de2bb…597f6d
Audit this contract →
← previous block·next block →recent activity