← previous blocknext block →recent activity
Analyzing
Block #90,224,609
34 transactions · 34 stateful · 2026-07-25 14:21:12 UTC
Parallelism
59/100
Blocked
65%
Avg conflicts / tx
3.21
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #90,224,609 · 34 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w28w310w311w414w515w616w017w118w219w320w421w522w623w724w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
28 touches
91 conflicts
0x55b4e430…44cb
0x754704…b603
28 touches
91 conflicts
0x00000000…0005
0x370e2e…63b4
26 touches
78 conflicts
0x1bff683e…7ecb
0x754704…b603
26 touches
78 conflicts
0x0053fc0f…e62f
0x0a2fbf…29b1
20 touches
45 conflicts
0x6e72a4a7…3617
0x0a2fbf…29b1
20 touches
45 conflicts
0x6e72a4a7…3618
0x0a2fbf…29b1
20 touches
45 conflicts
0x6e72a4a7…361b
0x0a2fbf…29b1
20 touches
45 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: 0x0a2fbf2d…f729b1
91 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity