← previous blocknext block →recent activity
Analyzing
Block #90,037,213
13 transactions · 13 stateful · 2026-07-24 22:33:42 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,037,213 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x679a6fa2…44c0
0x0a2fbf…29b1
6 touches
3 conflicts
0x679a6fa2…44c1
0x0a2fbf…29b1
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
6 touches
3 conflicts
0x679a6fa2…44c4
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0005
0x370e2e…63b4
4 touches
1 conflict
0x40c4c8ef…303b
0x0a2fbf…29b1
4 touches
1 conflict
0x40c4c8ef…303a
0x0a2fbf…29b1
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: 0x0a2fbf2d…f729b1
3 conflicts on slot 0x679a6fa222…8a44c0
Audit this contract →
← previous block·next block →recent activity