← previous blocknext block →recent activity
Analyzing
Block #90,028,779
16 transactions · 13 stateful · 2026-07-24 21:51:15 UTC
Parallelism
75/100
Blocked
54%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,028,779 · 16 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
1w02w03w15w18w19w010w111w213w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb874a6c…caa0
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x194876e0…27c6
0x34b655…2a6f
4 touches
1 conflict
0x199944d5…ab9f
0x34b655…2a6f
4 touches
1 conflict
0x1ed748d8…d530
0x34b655…2a6f
4 touches
1 conflict
0x1f6b228e…f0a0
0x34b655…2a6f
4 touches
1 conflict
0x22af2208…099e
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
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 0xfb874a6c9f…bfcaa0
Audit this contract →
← previous block·next block →recent activity