← previous blocknext block →recent activity
Analyzing
Block #90,836,522
12 transactions · 10 stateful · 2026-07-27 17:54:36 UTC
Parallelism
58/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,836,522 · 12 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
3w04w15w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0x00842ba8…bdc6
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x53e50026…6d8c
0x2b46c0…1669
2 touches
0 conflicts
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity