← previous blocknext block →recent activity
Analyzing
Block #90,630,470
25 transactions · 21 stateful · 2026-07-27 00:37:55 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,630,470 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w28w010w011w112w216w318w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1584b7d0…7266
0x34b655…2a6f
8 touches
6 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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 0x1584b7d0d7…317266
Audit this contract →
← previous block·next block →recent activity