← previous blocknext block →recent activity
Analyzing
Block #90,651,245
25 transactions · 19 stateful · 2026-07-27 02:22:25 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
0.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,651,245 · 25 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
1w07w08w19w210w011w312w414w515w117w220w623w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00c47ec5…dfee
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5b30a6e6…b249
0x34b655…2a6f
4 touches
1 conflict
0x6d94d7d6…6ed4
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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 0x00c47ec566…5cdfee
Audit this contract →
← previous block·next block →recent activity