← previous blocknext block →recent activity
Analyzing
Block #90,624,378
14 transactions · 14 stateful · 2026-07-27 00:07:16 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,624,378 · 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
4w05w06w09w110w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xdd38f4e6…586d
0x34b655…2a6f
4 touches
1 conflict
0x1408a100…f721
0x34b655…2a6f
4 touches
1 conflict
0x141a3ab6…f2cf
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0x8f518381…ae20
0x34b655…2a6f
4 touches
1 conflict
0x9cc36ddc…f1a3
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