← previous blocknext block →recent activity
Analyzing
Block #90,795,420
23 transactions · 20 stateful · 2026-07-27 14:27:44 UTC
Parallelism
78/100
Blocked
45%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,795,420 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w08w111w113w215w316w117w118w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51087f5a…61f7
0x34b655…2a6f
8 touches
6 conflicts
0x34e9c24b…86b9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x3d222a5e…ecac
0x34b655…2a6f
8 touches
6 conflicts
0x516f4295…fad1
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
6 conflicts on slot 0x51087f5abf…f061f7
Audit this contract →
← previous block·next block →recent activity