← previous blocknext block →recent activity
Analyzing
Block #90,624,957
22 transactions · 22 stateful · 2026-07-27 00:10:11 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,624,957 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w08w19w210w313w117w118w220w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xa164d951…1534
0xe1c8b7…3022
6 touches
3 conflicts
0x67d846dd…358c
0x526112…7777
6 touches
3 conflicts
0x33e1047c…f65a
0x9f3832…4ae4
6 touches
3 conflicts
0x7cf5136f…ba69
0x9f3832…4ae4
6 touches
3 conflicts
0xa4b7c8aa…4596
0x9f3832…4ae4
6 touches
3 conflicts
0xa4b7c8aa…4597
0x9f3832…4ae4
6 touches
3 conflicts
0x53bc68ea…13ad
0xe1c8b7…3022
6 touches
3 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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity