← previous blocknext block →recent activity
Analyzing
Block #89,679,789
14 transactions · 14 stateful · 2026-07-23 16:32:20 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,679,789 · 14 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
2w03w14w27w39w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc44901fe…0fef
0x34b655…2a6f
6 touches
3 conflicts
0x861e5aef…d32c
0x34b655…2a6f
6 touches
3 conflicts
0x51c8b4fa…003e
0x34b655…2a6f
6 touches
3 conflicts
0xdd1353c6…9780
0x34b655…2a6f
6 touches
3 conflicts
0x11ebadec…5b43
0x34b655…2a6f
6 touches
3 conflicts
0x4dd3fcaa…e1e2
0x34b655…2a6f
6 touches
3 conflicts
0x6f132c01…cdcd
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