← previous blocknext block →recent activity
Analyzing
Block #90,464,505
20 transactions · 19 stateful · 2026-07-26 10:42:59 UTC
Parallelism
60/100
Blocked
53%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,464,505 · 20 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
1w02w13w05w16w27w310w011w012w214w116w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5d321d…a474
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x607e481f…43e3
0x34b655…2a6f
6 touches
3 conflicts
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x4f9a134d…2c11
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
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