← previous blocknext block →recent activity
Analyzing
Block #90,232,728
22 transactions · 18 stateful · 2026-07-25 15:02:09 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,232,728 · 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
1w02w14w28w09w310w011w113w214w315w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xe6a7c855…2e38
0xd32edf…ff58
7 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x1136affa…48cb
0x34b655…2a6f
6 touches
3 conflicts
0x5110a94f…86d1
0x34b655…2a6f
4 touches
1 conflict
0x5110a94f…86d2
0x34b655…2a6f
4 touches
1 conflict
0x61d37f4f…61d2
0x34b655…2a6f
4 touches
1 conflict
0x62b26c37…87d6
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity