← previous blocknext block →recent activity
Analyzing
Block #89,578,021
16 transactions · 15 stateful · 2026-07-23 05:49:22 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,578,021 · 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
4w07w08w09w111w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ccb4355…c3e2
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x3ce98929…9a9b
0x34b655…2a6f
4 touches
1 conflict
0x4886b3df…67a3
0x34b655…2a6f
4 touches
1 conflict
0x0bee8017…c90a
0x34b655…2a6f
2 touches
0 conflicts
0x30c5329c…711c
0x34b655…2a6f
2 touches
0 conflicts
0x98862f54…62ca
0x34b655…2a6f
2 touches
0 conflicts
0xcf8e8419…c691
0x34b655…2a6f
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 0x7ccb4355e3…75c3e2
Audit this contract →
← previous block·next block →recent activity