← previous blocknext block →recent activity
Analyzing
Block #90,625,725
28 transactions · 23 stateful · 2026-07-27 00:14:02 UTC
Parallelism
61/100
Blocked
57%
Avg conflicts / tx
1.71
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #90,625,725 · 28 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w19w210w311w412w513w614w716w118w819w925w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
8 touches
6 conflicts
0x0c33bb29…c6a9
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x3b1ce1dd…dc2f
0x34b655…2a6f
6 touches
3 conflicts
0x917f99a5…7989
0x34b655…2a6f
6 touches
3 conflicts
0xa5ab7b8a…c97b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity