← previous blocknext block →recent activity
Analyzing
Block #90,789,379
18 transactions · 17 stateful · 2026-07-27 13:57:21 UTC
Parallelism
56/100
Blocked
65%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,789,379 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w36w47w09w510w111w412w013w114w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
8 touches
6 conflicts
0x820b2f6b…9263
0x34b655…2a6f
6 touches
3 conflicts
0x9ca52d19…da85
0x34b655…2a6f
6 touches
3 conflicts
0x05114fa1…7f23
0x34b655…2a6f
6 touches
3 conflicts
0x007892de…5752
0x34b655…2a6f
6 touches
3 conflicts
0x74c7e4b2…d9d3
0x34b655…2a6f
4 touches
1 conflict
0x78b60ad8…8468
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity