← previous blocknext block →recent activity
Analyzing
Block #90,817,613
18 transactions · 17 stateful · 2026-07-27 16:19:29 UTC
Parallelism
61/100
Blocked
41%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,817,613 · 18 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
2w03w05w06w17w28w310w412w513w615w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8814f69c…42b3
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xcd26fba5…21c6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…642d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x64275949…d698
0x34b655…2a6f
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
21 conflicts on slot 0x8814f69c3b…8042b3
Audit this contract →
← previous block·next block →recent activity