← previous blocknext block →recent activity
Analyzing
Block #90,812,126
23 transactions · 19 stateful · 2026-07-27 15:51:52 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,812,126 · 23 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
1w05w06w17w212w113w215w116w317w218w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x405da62e…192a
0xa6afd3…d132
6 touches
3 conflicts
0xb476ee35…c627
0xa6afd3…d132
6 touches
3 conflicts
0x5f56ffe5…09c0
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7743
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7744
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