← previous blocknext block →recent activity
Analyzing
Block #90,794,611
21 transactions · 19 stateful · 2026-07-27 14:23:40 UTC
Parallelism
76/100
Blocked
32%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,794,611 · 21 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
2w03w08w19w010w111w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd7badc5e…8c2b
0xa6afd3…d132
4 touches
1 conflict
0x449d101e…ea3f
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0x4c22021d…f8a7
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity