← previous blocknext block →recent activity
Analyzing
Block #90,803,590
22 transactions · 20 stateful · 2026-07-27 15:08:51 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,803,590 · 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
2w05w06w17w28w011w112w214w117w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ba6ae4a…90cb
0x34b655…2a6f
6 touches
3 conflicts
0x41377979…0a18
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x48e6051f…5350
0x34b655…2a6f
4 touches
1 conflict
0x4cf71e13…100c
0x34b655…2a6f
4 touches
1 conflict
0x5c16527f…628c
0x34b655…2a6f
4 touches
1 conflict
0x5d5e7cc3…011c
0x34b655…2a6f
4 touches
1 conflict
0x5e1144e3…ca4e
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 0x9ba6ae4a28…c990cb
Audit this contract →
← previous block·next block →recent activity