← previous blocknext block →recent activity
Analyzing
Block #89,388,482
14 transactions · 13 stateful · 2026-07-22 08:42:59 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,388,482 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8391fb68…4c83
0x34b655…2a6f
4 touches
1 conflict
0xb26fce3e…f47f
0x34b655…2a6f
4 touches
1 conflict
0xd2186d1c…b3c2
0x34b655…2a6f
4 touches
1 conflict
0x447777de…972b
0x34b655…2a6f
4 touches
1 conflict
0xe8058ec4…ebac
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity