← previous blocknext block →recent activity
Analyzing
Block #90,125,494
18 transactions · 16 stateful · 2026-07-25 06:01:39 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
0.72
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,125,494 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w18w29w310w411w112w513w214w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
6 touches
3 conflicts
0x94de4d05…ad01
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x3c955e7e…ef5e
0x34b655…2a6f
4 touches
1 conflict
0x3dae5ee1…721b
0x34b655…2a6f
4 touches
1 conflict
0x578c12b5…1fb8
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity