← previous blocknext block →recent activity
Analyzing
Block #90,805,697
14 transactions · 11 stateful · 2026-07-27 15:19:27 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,805,697 · 14 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
1w02w03w15w28w39w010w112w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e76cf03…9cc3
0x34b655…2a6f
8 touches
6 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0xf4d0bddb…07a4
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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 0x5e76cf0367…8a9cc3
Audit this contract →
← previous block·next block →recent activity