← previous blocknext block →recent activity
Analyzing
Block #90,638,335
15 transactions · 14 stateful · 2026-07-27 01:17:29 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,638,335 · 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
4w05w06w19w211w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0x94e68337…5eb0
0x34b655…2a6f
6 touches
3 conflicts
0x7e0e4900…187a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x363a4317…87d2
0x34b655…2a6f
4 touches
1 conflict
0x3737ed78…b290
0x34b655…2a6f
4 touches
1 conflict
0x3c1390ae…035a
0x34b655…2a6f
4 touches
1 conflict
0x44e45b51…5a2c
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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity