← previous blocknext block →recent activity
Analyzing
Block #90,688,693
14 transactions · 13 stateful · 2026-07-27 05:30:49 UTC
Parallelism
43/100
Blocked
62%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,688,693 · 14 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w37w110w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08330b36…ae29
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc244b288…db37
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xeb66ad8f…5f38
0x34b655…2a6f
6 touches
3 conflicts
0xff107718…55e9
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 0x08330b3687…a7ae29
Audit this contract →
← previous block·next block →recent activity