← previous blocknext block →recent activity
Analyzing
Block #89,378,324
16 transactions · 14 stateful · 2026-07-22 07:35:04 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,378,324 · 16 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
1w06w07w110w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xded5ec0c…f0fc
0x34b655…2a6f
4 touches
1 conflict
0xc08384da…ecb7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x1c1b5ec9…43f6
0x34b655…2a6f
4 touches
1 conflict
0x21d22421…0b7a
0x34b655…2a6f
4 touches
1 conflict
0x4560e5a8…b741
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 0xded5ec0c97…40f0fc
Audit this contract →
← previous block·next block →recent activity