← previous blocknext block →recent activity
Analyzing
Block #90,795,753
32 transactions · 18 stateful · 2026-07-27 14:29:25 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,795,753 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w116w017w118w219w320w422w123w528w029w130w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x3e0065ad…e39b
0x34b655…2a6f
4 touches
1 conflict
0x49c0b886…0748
0x34b655…2a6f
4 touches
1 conflict
0x617213e1…ef85
0x34b655…2a6f
4 touches
1 conflict
0x6b2ba712…0214
0x34b655…2a6f
4 touches
1 conflict
0x8f267639…ccff
0x34b655…2a6f
4 touches
1 conflict
0x92a5eb10…d5e3
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity