← previous blocknext block →recent activity
Analyzing
Block #90,945,353
23 transactions · 21 stateful · 2026-07-28 03:02:07 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,945,353 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w07w110w113w114w215w316w218w019w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2cb2bb3…7676
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x342fbbca…d443
0x40c49f…2af0
6 touches
3 conflicts
0xe2ed9efd…a0e7
0x40c49f…2af0
6 touches
3 conflicts
0x29c1a140…099f
0x34b655…2a6f
6 touches
3 conflicts
0xbd9491f7…dd92
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 0xd2cb2bb3d4…f87676
Audit this contract →
← previous block·next block →recent activity