← previous blocknext block →recent activity
Analyzing
Block #90,890,110
13 transactions · 12 stateful · 2026-07-27 22:24:13 UTC
Parallelism
77/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,890,110 · 13 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
2w03w16w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1adc270e…f7f6
0x34b655…2a6f
4 touches
1 conflict
0xabd0bcfc…64e2
0x34b655…2a6f
4 touches
1 conflict
0x3e8569e7…04d7
0x34b655…2a6f
2 touches
0 conflicts
0x4c188934…158e
0x34b655…2a6f
2 touches
0 conflicts
0x60ddbce7…4996
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