← previous blocknext block →recent activity
Analyzing
Block #89,563,578
18 transactions · 16 stateful · 2026-07-23 04:12:51 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,563,578 · 18 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
2w03w06w07w18w210w313w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacdb5a84…fff4
0x34b655…2a6f
8 touches
6 conflicts
0x10797f0b…439a
0x34b655…2a6f
4 touches
1 conflict
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x725005f3…5b0e
0x34b655…2a6f
4 touches
1 conflict
0x7c4c2932…21ae
0x34b655…2a6f
4 touches
1 conflict
0x88403d65…91a5
0x34b655…2a6f
4 touches
1 conflict
0x961c0cd9…0937
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 0xacdb5a84e8…3ffff4
Audit this contract →
← previous block·next block →recent activity