← previous blocknext block →recent activity
Analyzing
Block #90,787,353
22 transactions · 19 stateful · 2026-07-27 13:47:07 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,787,353 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w07w08w110w011w112w213w315w116w118w220w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x538f77c2…a9e7
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb8fccd1b…b5f2
0x2b46c0…1669
4 touches
1 conflict
0x5a3a03c4…e559
0x34b655…2a6f
4 touches
1 conflict
0x5eb5d9be…b2c1
0x34b655…2a6f
4 touches
1 conflict
0xa6c3f6bf…7fac
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