← previous blocknext block →recent activity
Analyzing
Block #89,701,114
12 transactions · 11 stateful · 2026-07-23 18:19:52 UTC
Parallelism
50/100
Blocked
55%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,701,114 · 12 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w16w28w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f4727d…cdb7
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3b666394…cae1
0x34b655…2a6f
6 touches
3 conflicts
0xc94a6349…4379
0x34b655…2a6f
6 touches
3 conflicts
0x9d9b4da9…ecf3
0x34b655…2a6f
4 touches
1 conflict
0x99479bc5…3a88
0x34b655…2a6f
4 touches
1 conflict
0xb54facbb…1914
0x34b655…2a6f
4 touches
1 conflict
0xb5cddf91…0abf
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
10 conflicts on slot 0xf2f4727df6…a5cdb7
Audit this contract →
← previous block·next block →recent activity