← previous blocknext block →recent activity
Analyzing
Block #90,790,729
16 transactions · 16 stateful · 2026-07-27 14:04:09 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,790,729 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w111w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0xf0ac75b4…3bd6
0x34b655…2a6f
3 touches
1 conflict
0x39c5ff72…c870
0x34b655…2a6f
2 touches
0 conflicts
0x50fd6f6f…2048
0x34b655…2a6f
2 touches
0 conflicts
0x519e0fef…7303
0x34b655…2a6f
2 touches
0 conflicts
0x55923b41…87ec
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity