← previous blocknext block →recent activity
Analyzing
Block #90,042,065
16 transactions · 16 stateful · 2026-07-24 22:58:12 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,042,065 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x370e2e…63b4
14 touches
21 conflicts
0x1bff683e…7ecb
0x754704…b603
14 touches
21 conflicts
0x00000000…0006
0x0a2fbf…29b1
14 touches
21 conflicts
0x55b4e430…44cb
0x754704…b603
14 touches
21 conflicts
0x4dd6eedb…bd47
0x0a2fbf…29b1
8 touches
6 conflicts
0x9816e924…7da5
0x0a2fbf…29b1
8 touches
6 conflicts
0x9816e924…7da6
0x0a2fbf…29b1
8 touches
6 conflicts
0x4dd6eedb…bd43
0x0a2fbf…29b1
8 touches
6 conflicts
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: 0x370e2ee6…bd63b4
21 conflicts on slot 0x0000000000…000005
Audit this contract →
← previous block·next block →recent activity