← previous blocknext block →recent activity
Analyzing
Block #90,124,672
7 transactions · 7 stateful · 2026-07-25 05:57:31 UTC
Parallelism
43/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,124,672 · 7 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa948bd93…b5dd
0x34b655…2a6f
6 touches
3 conflicts
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4b77c415…75b0
0x34b655…2a6f
4 touches
1 conflict
0x5ee8542f…9a7d
0x34b655…2a6f
4 touches
1 conflict
0x6e8a26ca…0257
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
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 0xa948bd939f…5bb5dd
Audit this contract →
← previous block·next block →recent activity