← previous blocknext block →recent activity
Analyzing
Block #90,840,144
11 transactions · 11 stateful · 2026-07-27 18:12:50 UTC
Parallelism
73/100
Blocked
18%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,840,144 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x663ab2c3…67ab
0x34b655…2a6f
6 touches
3 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe561281f…7569
0x34b655…2a6f
4 touches
1 conflict
0xe49fcffd…14f7
0x36878c…5c95
2 touches
0 conflicts
0xf3132618…0574
0x36878c…5c95
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
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
3 conflicts on slot 0x663ab2c30e…e367ab
Audit this contract →
← previous block·next block →recent activity