← previous blocknext block →recent activity
Analyzing
Block #90,027,221
18 transactions · 17 stateful · 2026-07-24 21:43:25 UTC
Parallelism
56/100
Blocked
41%
Avg conflicts / tx
0.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,027,221 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w211w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe867820f…154c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x50d44a56…fe50
0x34b655…2a6f
4 touches
1 conflict
0x6854b245…6d96
0x34b655…2a6f
4 touches
1 conflict
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x73670e81…2813
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
6 conflicts on slot 0xe867820f8c…f5154c
Audit this contract →
← previous block·next block →recent activity