← previous blocknext block →recent activity
Analyzing
Block #90,029,008
20 transactions · 16 stateful · 2026-07-24 21:52:24 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,029,008 · 20 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
3w05w17w08w19w010w111w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe57786b4…fddd
0x0a2fbf…29b1
14 touches
21 conflicts
0x4387a428…4389
0x0a2fbf…29b1
14 touches
21 conflicts
0x00000000…0006
0x0a2fbf…29b1
14 touches
21 conflicts
0xe57786b4…fdde
0x0a2fbf…29b1
14 touches
21 conflicts
0x00000000…0005
0x370e2e…63b4
14 touches
21 conflicts
0x1bff683e…7ecb
0x754704…b603
14 touches
21 conflicts
0x55b4e430…44cb
0x754704…b603
14 touches
21 conflicts
0x4387a428…4385
0x0a2fbf…29b1
14 touches
21 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
21 conflicts on slot 0xe57786b4f4…76fddd
Audit this contract →
← previous block·next block →recent activity