← previous blocknext block →recent activity
Analyzing
Block #89,744,838
14 transactions · 14 stateful · 2026-07-23 22:00:39 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,744,838 · 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
3w04w15w06w17w28w210w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x363a4317…87d2
0x34b655…2a6f
4 touches
1 conflict
0x36ce0155…1682
0x34b655…2a6f
4 touches
1 conflict
0x4783345c…4a90
0x34b655…2a6f
4 touches
1 conflict
0x4ac2a863…cba1
0x34b655…2a6f
4 touches
1 conflict
0x58d6b9cf…7c9e
0x34b655…2a6f
4 touches
1 conflict
0x63bed776…8d4a
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity