← previous blocknext block →recent activity
Analyzing
Block #90,628,559
25 transactions · 21 stateful · 2026-07-27 00:28:18 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,628,559 · 25 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
1w02w03w18w09w110w011w115w016w117w218w219w120w323w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3c543cf…207a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x24eaf46d…8c2e
0x34b655…2a6f
4 touches
1 conflict
0x4e58f1d6…2fca
0x34b655…2a6f
4 touches
1 conflict
0x634dddde…2af8
0x34b655…2a6f
4 touches
1 conflict
0x6630d365…74ad
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0xa3c543cf72…95207a
Audit this contract →
← previous block·next block →recent activity