← previous blocknext block →recent activity
Analyzing
Block #90,839,790
14 transactions · 12 stateful · 2026-07-27 18:11:03 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.64
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,839,790 · 14 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
2w03w05w06w18w29w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x26d1c221…4d2a
0x34b655…2a6f
6 touches
3 conflicts
0xe2e52e46…0894
0x34b655…2a6f
6 touches
3 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0x5af098c7…4807
0x34b655…2a6f
4 touches
1 conflict
0x663ab2c3…67ab
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
3 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity