← previous blocknext block →recent activity
Analyzing
Block #90,626,020
12 transactions · 11 stateful · 2026-07-27 00:15:31 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,626,020 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w28w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe470a235…a6ae
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x48e3acd8…cf41
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x2547d753…e8e6
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x366748e9…1282
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
6 conflicts on slot 0xe470a23573…9ca6ae
Audit this contract →
← previous block·next block →recent activity