← previous blocknext block →recent activity
Analyzing
Block #89,711,919
12 transactions · 11 stateful · 2026-07-23 19:14:19 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,711,919 · 12 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00893bb8…77ee
0x34b655…2a6f
4 touches
1 conflict
0x4f92c64e…9adc
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xab94749e…6100
0x1c8a33…d316
2 touches
0 conflicts
0xaf48c9f8…cc6c
0x1c8a33…d316
2 touches
0 conflicts
0xb64d9643…5616
0x1c8a33…d316
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 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: Perpl
1 conflict on slot 0x00893bb8a3…f777ee
Audit this contract →
← previous block·next block →recent activity