← previous blocknext block →recent activity
Analyzing
Block #90,450,096
15 transactions · 12 stateful · 2026-07-26 09:30:31 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,450,096 · 15 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
4w05w16w07w111w212w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5d321d…a474
0x34b655…2a6f
8 touches
6 conflicts
0x12659c8c…062e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x353a3a00…5e0a
0x34b655…2a6f
6 touches
3 conflicts
0x9fe82ab3…218f
0x34b655…2a6f
6 touches
3 conflicts
0xb9f50f91…13ef
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x1a5d321d5d…0da474
Audit this contract →
← previous block·next block →recent activity