← previous blocknext block →recent activity
Analyzing
Block #89,416,297
15 transactions · 13 stateful · 2026-07-22 11:48:57 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,416,297 · 15 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
1w02w13w06w110w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4681609f…6493
0x34b655…2a6f
8 touches
6 conflicts
0x95f74298…c204
0x34b655…2a6f
4 touches
1 conflict
0xd4d6916d…251b
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x3f641cba…6c96
0xd32edf…ff58
3 touches
1 conflict
0x5417eb8b…a873
0x065c9d…c394
2 touches
0 conflicts
0x9e17e3da…bbf8
0x065c9d…c394
2 touches
0 conflicts
0xc834d75c…e4c9
0x065c9d…c394
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
6 conflicts on slot 0x4681609fd4…e96493
Audit this contract →
← previous block·next block →recent activity