← previous blocknext block →recent activity
Analyzing
Block #89,860,823
11 transactions · 11 stateful · 2026-07-24 07:45:48 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,860,823 · 11 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
4w05w16w27w39w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x207e3d13…166b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3d4c0233…20a5
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9e49f754…23a2
0x34b655…2a6f
4 touches
1 conflict
0xb5a3b1be…8122
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 0x207e3d13f1…9d166b
Audit this contract →
← previous block·next block →recent activity