← previous blocknext block →recent activity
Analyzing
Block #89,871,223
16 transactions · 16 stateful · 2026-07-24 08:38:07 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,871,223 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w112w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5f761f5…e897
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0490581d…adaf
0x34b655…2a6f
4 touches
1 conflict
0x04b5a023…e9ba
0x34b655…2a6f
4 touches
1 conflict
0x3df0422c…fd38
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
1 conflict on slot 0xa5f761f512…0de897
Audit this contract →
← previous block·next block →recent activity