← previous blocknext block →recent activity
Analyzing
Block #90,795,576
25 transactions · 21 stateful · 2026-07-27 14:28:31 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,795,576 · 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
1w02w14w05w07w110w011w012w015w116w217w218w119w121w222w323w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x12d867cc…b97c
0x34b655…2a6f
6 touches
3 conflicts
0x731f2745…9370
0xa6afd3…d132
6 touches
3 conflicts
0xf18906a6…d2e3
0x34b655…2a6f
6 touches
3 conflicts
0xb5c4826d…bdd6
0x2b46c0…1669
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity