← previous blocknext block →recent activity
Analyzing
Block #90,560,783
17 transactions · 16 stateful · 2026-07-26 18:47:20 UTC
Parallelism
59/100
Blocked
56%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,560,783 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w18w210w311w413w214w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecf72a3c…67a3
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x8743e1ba…8331
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x10379e8d…3675
0x34b655…2a6f
6 touches
3 conflicts
0x709c2293…6c56
0x34b655…2a6f
4 touches
1 conflict
0x88dca381…45aa
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 0xecf72a3cf0…7b67a3
Audit this contract →
← previous block·next block →recent activity