← previous blocknext block →recent activity
Analyzing
Block #90,023,932
13 transactions · 13 stateful · 2026-07-24 21:26:50 UTC
Parallelism
54/100
Blocked
54%
Avg conflicts / tx
1.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,023,932 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w26w38w49w511w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0x89935301…af69
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xe8d8a9a2…40f3
0x34b655…2a6f
6 touches
3 conflicts
0x5f56ffe5…09c0
0x34b655…2a6f
6 touches
3 conflicts
0x73d460b4…c20c
0x34b655…2a6f
6 touches
3 conflicts
0x62af5969…79fb
0x34b655…2a6f
4 touches
1 conflict
0x62af5969…79fc
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
15 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity