← previous blocknext block →recent activity
Analyzing
Block #90,454,718
14 transactions · 14 stateful · 2026-07-26 09:53:46 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,454,718 · 14 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
4w06w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2ffa1f3…d3ae
0x34b655…2a6f
6 touches
3 conflicts
0xf06cb710…1a9a
0x34b655…2a6f
4 touches
1 conflict
0x8d7e3f62…e2cd
0x34b655…2a6f
4 touches
1 conflict
0xa33b7390…9e89
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xde95b18d…3751
0x34b655…2a6f
4 touches
1 conflict
0x08803a9b…dfbd
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 0xd2ffa1f3c7…48d3ae
Audit this contract →
← previous block·next block →recent activity