← previous blocknext block →recent activity
Analyzing
Block #90,969,474
16 transactions · 13 stateful · 2026-07-28 05:03:27 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,969,474 · 16 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
1w05w111w012w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x99701186…1cbf
0x34b655…2a6f
8 touches
6 conflicts
0xd68311fc…ac0d
0x34b655…2a6f
6 touches
3 conflicts
0xc857b971…0bcf
0x34b655…2a6f
6 touches
3 conflicts
0x1d6ce97a…901b
0x34b655…2a6f
4 touches
1 conflict
0xccb8c4ac…aa07
0x34b655…2a6f
4 touches
1 conflict
0x6d6ee110…e9af
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity