← previous blocknext block →recent activity
Analyzing
Block #89,563,331
16 transactions · 13 stateful · 2026-07-23 04:11:12 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,563,331 · 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
2w05w16w28w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2debe664…1818
0x34b655…2a6f
4 touches
1 conflict
0x9db3090e…7fb8
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xcd5c0ecb…4b5f
0x34b655…2a6f
4 touches
1 conflict
0xd192f4ed…d7ec
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfe65bb7b…12d7
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 0x2debe6641f…b31818
Audit this contract →
← previous block·next block →recent activity