← previous blocknext block →recent activity
Analyzing
Block #90,804,870
28 transactions · 24 stateful · 2026-07-27 15:15:17 UTC
Parallelism
86/100
Blocked
46%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,804,870 · 28 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
1w02w13w04w17w08w19w010w113w216w018w319w120w221w325w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xb476ee35…c627
0xa6afd3…d132
6 touches
3 conflicts
0x4bc1abab…5874
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x88066eb3…2501
0x34b655…2a6f
4 touches
1 conflict
0x91afe19d…3739
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 0xf3d10975b0…050d07
Audit this contract →
← previous block·next block →recent activity